project deliverables version 8: 11/23/04 final final version for first semester

27
Project Deliverables Project Deliverables Version 8: 11/23/04 Version 8: 11/23/04 Final Final Version for First Final Final Version for First Semester Semester

Upload: griffin-marsh

Post on 20-Jan-2018

232 views

Category:

Documents


0 download

DESCRIPTION

Format of Deliverables All Deliverables will be via CD. All Deliverables will be via CD. Outside: Surface of CD is to clearly indicate your course number and the team number, as CEN Team 2 or CIS 4327 – Team5. Also include the project title. Outside: Surface of CD is to clearly indicate your course number and the team number, as CEN Team 2 or CIS 4327 – Team5. Also include the project title. Inside: Each deliverable will be in a separate folder on the same CD, so when I access the CD, all I should see are individual folders with labels such as Deliverable n, as in Deliverable 4. Inside: Each deliverable will be in a separate folder on the same CD, so when I access the CD, all I should see are individual folders with labels such as Deliverable n, as in Deliverable 4.

TRANSCRIPT

Page 1: Project Deliverables Version 8: 11/23/04 Final Final Version for First Semester

Project DeliverablesProject Deliverables

Version 8: 11/23/04Version 8: 11/23/04Final Final Version for First Final Final Version for First

SemesterSemester

Page 2: Project Deliverables Version 8: 11/23/04 Final Final Version for First Semester

Overview of GuidanceOverview of Guidance I shall try to upgrade / refine I shall try to upgrade / refine

guidance for each deliverable as we guidance for each deliverable as we progress. progress.

Please view this file often as it will Please view this file often as it will change.change.

Suggestions for clarity and/or Suggestions for clarity and/or consistency are always welcome.consistency are always welcome.

Page 3: Project Deliverables Version 8: 11/23/04 Final Final Version for First Semester

Format of DeliverablesFormat of Deliverables All Deliverables will be via CD. All Deliverables will be via CD. OutsideOutside: Surface of CD is to clearly indicate : Surface of CD is to clearly indicate

your course number and the team number, your course number and the team number, as CEN 6016 - Team 2 or CIS 4327 – as CEN 6016 - Team 2 or CIS 4327 – Team5. Also include the project title.Team5. Also include the project title.

InsideInside: Each deliverable will be in a separate : Each deliverable will be in a separate folder on the same CD, so when I access the folder on the same CD, so when I access the CD, all I should see are individual folders CD, all I should see are individual folders with labels such as Deliverable n, as in with labels such as Deliverable n, as in Deliverable 4. Deliverable 4.

Page 4: Project Deliverables Version 8: 11/23/04 Final Final Version for First Semester

Contents of Folder Contents of Folder Team Num file,Team Num file, with file name as follows (for example): with file name as follows (for example):

Team3.TeamNumFile.Deliverable2.Date.09.27.04 Team3.TeamNumFile.Deliverable2.Date.09.27.04 In this file, you are to simply (may be a single Word file)In this file, you are to simply (may be a single Word file)::

List the names of the team members List the names of the team members Indicate who is team leader with phone number.Indicate who is team leader with phone number. List individual email accounts. List individual email accounts.

Iteration PlanIteration Plan with file name: with file name: Team3.IterationPlan.Deliverable2.Date.09.27.04 Team3.IterationPlan.Deliverable2.Date.09.27.04

(Omit for Inception and Elaboration…(Omit for Inception and Elaboration… Deliverables 1-5 this Deliverables 1-5 this term…)term…)

Note that the Iteration Plan will change for each deliverable, Note that the Iteration Plan will change for each deliverable, that is, it will be that is, it will be refined and ‘extendedrefined and ‘extended.’ The current iteration .’ The current iteration and a skeletal version of the next iteration constitute the and a skeletal version of the next iteration constitute the ‘extensions.’ Each successive deliverable will contain a ‘extensions.’ Each successive deliverable will contain a ‘revised’ Iteration Plan.‘revised’ Iteration Plan.

For first deliverable or two, may be more descriptive. For For first deliverable or two, may be more descriptive. For subsequent iterations, plan will be more cryptic, perhaps tabular. subsequent iterations, plan will be more cryptic, perhaps tabular. Not much verbiage. Not much verbiage.

Page 5: Project Deliverables Version 8: 11/23/04 Final Final Version for First Semester

Continued…Continued… EExecutive Summary (in xecutive Summary (in Word) Word) with file name:with file name:

Team3.ExecutiveSummary.Deliverable2.Date.09.27.04Team3.ExecutiveSummary.Deliverable2.Date.09.27.04 This single page document is to summarize the contents of This single page document is to summarize the contents of

this folderthis folder. . What ‘activities’ were undertakenWhat ‘activities’ were undertaken What ‘artifacts’ were changed and rationaleWhat ‘artifacts’ were changed and rationale Note: revising artifacts is the norm in an iterative Note: revising artifacts is the norm in an iterative

approach to software development. approach to software development. What What newnew ‘artifacts’ were produced ‘artifacts’ were produced

ArtifactsArtifacts - a - a FolderFolder Goal: Contains sub folders and single files as appropriate.Goal: Contains sub folders and single files as appropriate.

E.g. Should have a folder for Rose Models; Folder for Use Cases; E.g. Should have a folder for Rose Models; Folder for Use Cases; perhaps a simple Word files for, say, Risks List, Business Rules, perhaps a simple Word files for, say, Risks List, Business Rules, Vision Document, etc… But you may group these Word files into a Vision Document, etc… But you may group these Word files into a folder called Management Documents; You have some flexibility folder called Management Documents; You have some flexibility here. Clear organization is a must.here. Clear organization is a must.

New artifacts or revisited artifacts from previous deliverables, New artifacts or revisited artifacts from previous deliverables, - specific - specific componentscomponents of the deliverable should be found of the deliverable should be found here, and a number of these should be in their own subfolder, here, and a number of these should be in their own subfolder, such as the user interface prototype, Use Case diagrams, use such as the user interface prototype, Use Case diagrams, use case narratives, analysis model, sequence diagrams, etc.case narratives, analysis model, sequence diagrams, etc.

Page 6: Project Deliverables Version 8: 11/23/04 Final Final Version for First Semester

Guidance on the Rose Guidance on the Rose BrowserBrowser

Use Case Diagrams in Use Case Folder within Use Use Case Diagrams in Use Case Folder within Use Case Model in RoseCase Model in Rose Each Use Case is to be a separate subfolder in the Use Each Use Case is to be a separate subfolder in the Use

Case folder within Use Case Model (see the Rose Browser).Case folder within Use Case Model (see the Rose Browser). But Use Case Narratives are in Requisite Pro for Grad But Use Case Narratives are in Requisite Pro for Grad

Students.Students. Actors in folder within Use Case Model in RoseActors in folder within Use Case Model in Rose Look very much at Team2 – Requisite Pro top level Look very much at Team2 – Requisite Pro top level

folders BEFORE deciding on deliverable contents if folders BEFORE deciding on deliverable contents if you are a grad student!!!!!you are a grad student!!!!!

Business Vision and Glossary in folders – See Team Business Vision and Glossary in folders – See Team 22

Page 7: Project Deliverables Version 8: 11/23/04 Final Final Version for First Semester

Grammar and WordingGrammar and Wording Under NO circumstances will poor grammar or ill-Under NO circumstances will poor grammar or ill-

conceived sentences be considered acceptable work. conceived sentences be considered acceptable work. EACH portion of EACH deliverable should be reviewed EACH portion of EACH deliverable should be reviewed

and ‘signed off’ by EACH team member.and ‘signed off’ by EACH team member. Poor adherence to this ‘standard’ will impact EACH Poor adherence to this ‘standard’ will impact EACH

team member. So, check out your text BEFORE you team member. So, check out your text BEFORE you submit it to me.submit it to me.

This is a TEAM responsibility!!This is a TEAM responsibility!! On the provided templates, there is room for signoff On the provided templates, there is room for signoff

by the team / team members. Use this for by the team / team members. Use this for verification…verification…

Page 8: Project Deliverables Version 8: 11/23/04 Final Final Version for First Semester

Deliverable #1 The Business CaseDeliverable #1 The Business CaseDue: Wednesday 10/4Due: Wednesday 10/4

Purpose: Purpose: To understand the structure and dynamics of the To understand the structure and dynamics of the organization within which organization within which the application will operatethe application will operate;;To ensure customers, end-users, and developers understand the To ensure customers, end-users, and developers understand the organization;organization;To derive requirements on systems to support the organization;To derive requirements on systems to support the organization;To support these, a number of models and documents are needed. To support these, a number of models and documents are needed. Deliverable Artifacts:Deliverable Artifacts:

Business use case modelBusiness use case modelUse Cases and Actors - ModeledUse Cases and Actors - Modeled

Business object modelBusiness object modelUse Cases realized with actors and entities for the modelingUse Cases realized with actors and entities for the modelingUse Cases realized with actors for the Use Case Descriptions.Use Cases realized with actors for the Use Case Descriptions.

Additional Artifacts Additional Artifacts Business Vision document - textBusiness Vision document - textBusiness Glossary - textBusiness Glossary - textBusiness Rules – textBusiness Rules – text

Business Risk List - textBusiness Risk List - textDomain Model - model in Rational Rose (in next deliverable)Domain Model - model in Rational Rose (in next deliverable)

Page 9: Project Deliverables Version 8: 11/23/04 Final Final Version for First Semester

Guidance on Deliverable #1Guidance on Deliverable #1The Vision DocumentThe Vision Document

Use the templates provided. (You may use Requisite Pro if Use the templates provided. (You may use Requisite Pro if desired. Take the Requisite Pro Quick Tour…)desired. Take the Requisite Pro Quick Tour…)

This is an This is an essential documentessential document and should provide a list of and should provide a list of ‘features’ that the application to be developed should ‘features’ that the application to be developed should possess.possess.

These features are not behavioral (like the Use Cases). These features are not behavioral (like the Use Cases). These are text descriptions. Example of features:These are text descriptions. Example of features:

ClassicsCD.com Web ShopClassicsCD.com Web ShopSecure payment method.Secure payment method.Easy browsing for available titles.Easy browsing for available titles.Ability to check the status of an order.Ability to check the status of an order.Customer shall receive e-mail notification.Customer shall receive e-mail notification.The catalog shall be highly scaleable to include many The catalog shall be highly scaleable to include many titles and effective searching through those titles.titles and effective searching through those titles.Customer shall be able to customize the Web site.Customer shall be able to customize the Web site.Customer shall be able to register as a user for future Customer shall be able to register as a user for future purchases without needing to re-enter personal purchases without needing to re-enter personal information.information.

Page 10: Project Deliverables Version 8: 11/23/04 Final Final Version for First Semester

Guidance on Deliverable #1Guidance on Deliverable #1The Business CaseThe Business Case

Use the appropriate forms available at:Use the appropriate forms available at: RUP document templates are located at the site RUP document templates are located at the site

http://http://jdbv.sourceforge.net/RUP.htmljdbv.sourceforge.net/RUP.html.  .  The link for the Business Rules template is The link for the Business Rules template is

incorrect (points to the Business Modeling incorrect (points to the Business Modeling Guidelines template), so there is another link to Guidelines template), so there is another link to point to the Business Rules format.point to the Business Rules format.

There are also two former student examples on There are also two former student examples on my web page to guide you. (Note: I am not my web page to guide you. (Note: I am not disclosing their grades, or how I graded them.) disclosing their grades, or how I graded them.) These are merely samples of what they submitted.These are merely samples of what they submitted.

Page 11: Project Deliverables Version 8: 11/23/04 Final Final Version for First Semester

Guidance on Deliverable #1Guidance on Deliverable #1The Business CaseThe Business Case

When logging onto Rose, be sure to select RUP icon from When logging onto Rose, be sure to select RUP icon from the initial window.the initial window.

Be also certain to notice the tool mentors – when you select Be also certain to notice the tool mentors – when you select a folder in the Rose Browser, a description often appears a folder in the Rose Browser, a description often appears with invaluable information.with invaluable information.

The Business Use Case Model should be found in the Use The Business Use Case Model should be found in the Use Case View; Case View; This is a single model of the key business processes of the This is a single model of the key business processes of the

organization.organization. Business Object Model in the Logical View.Business Object Model in the Logical View. All business object models and the business use case model All business object models and the business use case model

are to be in a SINGLE copy of Rose.are to be in a SINGLE copy of Rose. (See examples on my web page.)(See examples on my web page.) Put your Business Object Models within the Business Object Put your Business Object Models within the Business Object

Model folder within Logical View in Rose – see examples on Model folder within Logical View in Rose – see examples on web page.web page.

Business object models are realizations of each of the business Business object models are realizations of each of the business use cases and contain business actors. (All domain-oriented)use cases and contain business actors. (All domain-oriented)

Page 12: Project Deliverables Version 8: 11/23/04 Final Final Version for First Semester

Deliverable #2Deliverable #2 Domain ModelDomain Modeland Statement of Work and Statement of Work

Due: October 13thDue: October 13th Develop the Domain ModelDevelop the Domain Model Iterate previous deliverable artifactsIterate previous deliverable artifacts

This means address EACH component and This means address EACH component and fix/repair/enhance/improve, etc. and certify.fix/repair/enhance/improve, etc. and certify.

Don’t make the same mistakes twice.Don’t make the same mistakes twice. Add a Statement of Work (SOW), that is, Add a Statement of Work (SOW), that is,

what is your team plan – who does what, what is your team plan – who does what, what is your plan, etc. (See textbook)what is your plan, etc. (See textbook)

Page 13: Project Deliverables Version 8: 11/23/04 Final Final Version for First Semester

Guidance on Deliverable #2 - Domain Guidance on Deliverable #2 - Domain ModelModel

In In additionaddition to standard items, this deliverable requires a complete Domain to standard items, this deliverable requires a complete Domain Model. The Domain Model is essential to understanding the environment Model. The Domain Model is essential to understanding the environment within which the application to be developed will function. Include also a within which the application to be developed will function. Include also a Statement of Work.Statement of Work.Turn in CD that contains all models and has links to text descriptions. Turn in CD that contains all models and has links to text descriptions.

Purpose:Purpose: Construct Domain Model (precursor activity to Use Case development)Construct Domain Model (precursor activity to Use Case development) Is an essential activity to facilitate good use case development that contains glossary items and objects Is an essential activity to facilitate good use case development that contains glossary items and objects

from the problem space (domain).from the problem space (domain).

Deliverable Artifacts for Deliverable #2:Deliverable Artifacts for Deliverable #2: Domain Model – taking into consideration additional attributes, multiplicities, associations, Domain Model – taking into consideration additional attributes, multiplicities, associations,

etc. The Domain Model should be captured as a etc. The Domain Model should be captured as a separate folderseparate folder under the Logical View under the Logical View in your Rose Browser.in your Rose Browser.

Statement of Work - a Word Document. See textbook and/or templates for formatStatement of Work - a Word Document. See textbook and/or templates for format

Other artifacts from Deliverable #1 to beOther artifacts from Deliverable #1 to be revisited. revisited. (Exec Summary will (Exec Summary will cite what changescite what changes you have done to each artifact…) you have done to each artifact…)

Business use case modelBusiness use case modelUse Cases and Actors - ModeledUse Cases and Actors - ModeledBusiness object modelBusiness object modelBusiness Vision document - textBusiness Vision document - textBusiness Glossary - textBusiness Glossary - textBusiness Rules - textBusiness Rules - text

Page 14: Project Deliverables Version 8: 11/23/04 Final Final Version for First Semester

Guidance on Deliverable #2: Domain Guidance on Deliverable #2: Domain ModelModel

Be certain to see example link on my web page and study Be certain to see example link on my web page and study carefully the slides in the appropriate two lectures. carefully the slides in the appropriate two lectures.

Be certain to fully consider my grading notes to you for Be certain to fully consider my grading notes to you for Deliverable #1 prior to submission of Deliverable #2.Deliverable #1 prior to submission of Deliverable #2.

For first deliverable or two, the Iteration Plan may For first deliverable or two, the Iteration Plan may be more ‘descriptive;’ that is, may contain be more ‘descriptive;’ that is, may contain textual descriptions. For textual descriptions. For subsequent iterations, plan subsequent iterations, plan will be more cryptic, perhaps bulleted, perhaps tabular. will be more cryptic, perhaps bulleted, perhaps tabular.

Not much verbiage. Activities undertaken, schedule, Not much verbiage. Activities undertaken, schedule, developers, results…developers, results…

Page 15: Project Deliverables Version 8: 11/23/04 Final Final Version for First Semester

Deliverable #3 - Use Case - Façade Deliverable #3 - Use Case - Façade Iteration plus Initial User Interface Iteration plus Initial User Interface

Prototype Prototype due: Monday 10/25due: Monday 10/25

Executive Summary (overviews new artifacts Executive Summary (overviews new artifacts and ALL changes/revisions to existing artifacts, and ALL changes/revisions to existing artifacts, such as the revised Iteration Plan, etc. as such as the revised Iteration Plan, etc. as required.required.

Specific Work:Specific Work: Revisit the Business Case (Deliverables 1 and 2) Revisit the Business Case (Deliverables 1 and 2)

including artifacts listed below and update them. including artifacts listed below and update them. (Risks Lists; Business Rules; Domain Model; (Risks Lists; Business Rules; Domain Model; Statement of Work, etc.)Statement of Work, etc.)

Include an index (numbered) for Use Cases that Include an index (numbered) for Use Cases that follow. (discussed in class and via slides)follow. (discussed in class and via slides) Use Case Index is to contain a number, Use Case Use Case Index is to contain a number, Use Case

name, short description, and other high level items name, short description, and other high level items you consider important. Construct this in tabular you consider important. Construct this in tabular form using a table in Word. See power point slides form using a table in Word. See power point slides for detailed attributes neededfor detailed attributes needed

Page 16: Project Deliverables Version 8: 11/23/04 Final Final Version for First Semester

Guidance on Façade Guidance on Façade IterationIteration

Develop an overall Use Case Model (all application Develop an overall Use Case Model (all application Use Cases and Actors). Similar to Business Use Use Cases and Actors). Similar to Business Use Case Model.Case Model.

Develop Develop Façade Use Case DescriptionsFaçade Use Case Descriptions and and associated associated Use Case Diagrams for each Use Case. for each Use Case.

Use Rose (Use Case View) for your models. Link the Use Rose (Use Case View) for your models. Link the Use Case Description text and ensure these Use Case Description text and ensure these descriptions are on the CD you turn in for grading. descriptions are on the CD you turn in for grading.

CEN 6016 students must use Requisite Pro*CEN 6016 students must use Requisite Pro* Model your Façade Use Cases using the Kulak and Model your Façade Use Cases using the Kulak and

Guiney book. Again, see power point lectures for Guiney book. Again, see power point lectures for required attributesrequired attributes. .

Additional information: Visual Modeling book and Additional information: Visual Modeling book and Rose Basics (see power point lecture slides for Rose Basics (see power point lecture slides for examples on including your Use Cases in your Rose examples on including your Use Cases in your Rose Model in the Use Case View.)Model in the Use Case View.)

Page 17: Project Deliverables Version 8: 11/23/04 Final Final Version for First Semester

Guidance onGuidance on: Facade Iteration: Facade Iteration Remember that the Façade iteration names Remember that the Façade iteration names

the use case, identifies actors, provides a the use case, identifies actors, provides a short description, frequently includes pre- and short description, frequently includes pre- and post conditions, triggers, etc. But it does NOT post conditions, triggers, etc. But it does NOT include the detailed actor-system interactions.include the detailed actor-system interactions.

See lecture notes for required attributes.See lecture notes for required attributes. Must include all Use Cases.Must include all Use Cases. Include your single Use Case Model in the Use Include your single Use Case Model in the Use

Case View (in Rose) in the folder provided by Case View (in Rose) in the folder provided by Rose. Note: this is NOT the Business Use Rose. Note: this is NOT the Business Use Case Model, which has been completed; Case Model, which has been completed; more, the icons are different for the actors and more, the icons are different for the actors and use cases. Be sure to note the differences.use cases. Be sure to note the differences.

Page 18: Project Deliverables Version 8: 11/23/04 Final Final Version for First Semester

Guidance on User Interface PrototypeGuidance on User Interface Prototype Develop User Interface Prototype…needed for Develop User Interface Prototype…needed for

requirements capture!!! Iterate this a as needed. requirements capture!!! Iterate this a as needed. (Should be done in conjunction with the Façade Use (Should be done in conjunction with the Façade Use Case and will (together with Domain Model) greatly Case and will (together with Domain Model) greatly assist you for Deliverable #4, your full-blown Use Case assist you for Deliverable #4, your full-blown Use Case Descriptions with alternate and exception paths.Descriptions with alternate and exception paths.

You may use any prototyping tool you wish: VB, Java, You may use any prototyping tool you wish: VB, Java, etc. Your prototype should include storyboarding.etc. Your prototype should include storyboarding. Most teams use static html; some use Front Page; some Most teams use static html; some use Front Page; some

contain Javascript, etc.contain Javascript, etc. Recommend testing your interface with someone from a Recommend testing your interface with someone from a

different group. If you link up with me, I will be glad to assist.different group. If you link up with me, I will be glad to assist. To accompany the Façade Use Cases, user interface To accompany the Façade Use Cases, user interface

prototype needs to be total complete. While we are not prototype needs to be total complete. While we are not including actor – application ‘interchanges,’ these are including actor – application ‘interchanges,’ these are essential for the next deliverable. essential for the next deliverable.

See examples of initial user interface prototypes on See examples of initial user interface prototypes on my web page.my web page.

See also (ahead) lecture slides on User Interface See also (ahead) lecture slides on User Interface DesignDesign

Page 19: Project Deliverables Version 8: 11/23/04 Final Final Version for First Semester

Deliverable #4Deliverable #4Full Use Cases Model & Activity Full Use Cases Model & Activity

DiagramsDiagramsdue: 11/8due: 11/8

Executive SummaryExecutive Summary Develop Focused and Filled Use Case Descriptions and Develop Focused and Filled Use Case Descriptions and

associated Use Case Diagrams for each Use Case.associated Use Case Diagrams for each Use Case. Use Rose (Use Case View) and Requisite Pro*Use Rose (Use Case View) and Requisite Pro* Kulak and Guiney book (Use Cases); Visual Modeling book Kulak and Guiney book (Use Cases); Visual Modeling book

and Rose Basics (see power point lecture slides for and Rose Basics (see power point lecture slides for examples.)examples.)

EachEach Use Case is to be accompanied by an Activity Diagram Use Case is to be accompanied by an Activity Diagram that should indicate flow for all paths in the Use Casethat should indicate flow for all paths in the Use Case

*CEN 6016 Students only*CEN 6016 Students only (Recognize that Use Cases are really never ‘finished.’)(Recognize that Use Cases are really never ‘finished.’) Your Use Case Diagrams will likely be supplemented with Your Use Case Diagrams will likely be supplemented with

Included or Extended Use Cases, as appropriate. Redo your Included or Extended Use Cases, as appropriate. Redo your Use Case Model for the Application.Use Case Model for the Application.

Page 20: Project Deliverables Version 8: 11/23/04 Final Final Version for First Semester

Guidance on Deliverable #4: Guidance on Deliverable #4: ‘Complete’ Use Case Model‘Complete’ Use Case Model

Executive Summary – as usual; All on CD.Executive Summary – as usual; All on CD. Complete Complete Use Case Model and Use Case Diagrams for for

eacheach Use Case – Use Case – This is a major assignmentThis is a major assignment. Consider . Consider alternative, exception flows, and ‘sub-flows’, using alternative, exception flows, and ‘sub-flows’, using extension points as appropriate.extension points as appropriate.

Reflect any use cases you feel are ‘included’ or Reflect any use cases you feel are ‘included’ or ‘extending.’ ‘extending.’

Activity DiagramsActivity Diagrams – one per Use Case (should include – one per Use Case (should include all alternate paths) (Include as package in Rose Model)all alternate paths) (Include as package in Rose Model)

Put Use Cases into groups – packages that ‘seem’ to go Put Use Cases into groups – packages that ‘seem’ to go together functionally, like the GUI or those that address together functionally, like the GUI or those that address business activities. business activities. (These will help in our architecture – as these will become (These will help in our architecture – as these will become

likely subsystems).likely subsystems). Iterate on the Use Case Model and/or your User Iterate on the Use Case Model and/or your User

Interface Prototype (and any other documents) from Interface Prototype (and any other documents) from Deliverable #3 as appropriateDeliverable #3 as appropriate

Page 21: Project Deliverables Version 8: 11/23/04 Final Final Version for First Semester

Guidance on Deliverable #4: Guidance on Deliverable #4: ‘Complete’ Use Case Model‘Complete’ Use Case Model

Allocate functional requirements to use casesAllocate functional requirements to use cases via the stories of via the stories of interchange. (and domain objects) This is a painstaking and interchange. (and domain objects) This is a painstaking and long task! It will underpin your entire design. Spend time long task! It will underpin your entire design. Spend time here!!!! Recognize that Use Cases are NOT functional here!!!! Recognize that Use Cases are NOT functional requirements; rather, they are stories of actor-application requirements; rather, they are stories of actor-application interactions which contain the required functionality.interactions which contain the required functionality.

Requirements with extension points to address alternate and Requirements with extension points to address alternate and exception flows. – see class notes.exception flows. – see class notes.

AllAll customer functionality should be accounted for here. Be customer functionality should be accounted for here. Be certain to use your Domain Model and italicize or bold all certain to use your Domain Model and italicize or bold all references to entities in the domain model.references to entities in the domain model.

Ensure everything the customer desires is accounted for!Ensure everything the customer desires is accounted for!

Page 22: Project Deliverables Version 8: 11/23/04 Final Final Version for First Semester

Keep the alternatives /exceptions WITH the use case. They Keep the alternatives /exceptions WITH the use case. They should be included with the use case and not made should be included with the use case and not made separate. See examples on web page.separate. See examples on web page.

Use the Use the User-Interface to ensure all functionality is User-Interface to ensure all functionality is captured. captured.

Develop Activity Diagrams – one Develop Activity Diagrams – one perper Use Case – that Use Case – that captures all paths (scenarios) in a Use Case. See Visual captures all paths (scenarios) in a Use Case. See Visual Modeling text for examples and use Rose.Modeling text for examples and use Rose.

Activity Diagrams should be placed in the Use Case View Activity Diagrams should be placed in the Use Case View under Use Case Models in a Folder entitled Activity under Use Case Models in a Folder entitled Activity DiagramsDiagrams

Page 23: Project Deliverables Version 8: 11/23/04 Final Final Version for First Semester

Deliverable #5 - Developing the Analysis Deliverable #5 - Developing the Analysis Model and Non-Functional Requirements - Model and Non-Functional Requirements - due 12/01due 12/01 Analysis Model (Preliminary Design)Analysis Model (Preliminary Design)

Contains communicating Contains communicating boundary, control, entity boundary, control, entity objects with relationshipsobjects with relationships, etc. , etc.

Will flow from your use case narratives and prototypeWill flow from your use case narratives and prototype Supports Interaction Modeling and much more…Supports Interaction Modeling and much more… Designed to lead ultimately to the class model (static)Designed to lead ultimately to the class model (static)

Sources: Use your prototype (boundary) again, Sources: Use your prototype (boundary) again, domain model (entities), and use case domain model (entities), and use case descriptions (control) in earnest. They are not descriptions (control) in earnest. They are not enough, but will help. See also your Vision enough, but will help. See also your Vision Document.Document. See Visual ModelingSee Visual Modeling Book; RUP; Logical View on RoseBook; RUP; Logical View on Rose

Page 24: Project Deliverables Version 8: 11/23/04 Final Final Version for First Semester

Guidance on Deliverable #5 Analysis Guidance on Deliverable #5 Analysis ModelModel

Include boundary classes together, control Include boundary classes together, control classes together, and entity classes together all classes together, and entity classes together all without associations to other classes. (a one-without associations to other classes. (a one-page drawing) This should partition all the page drawing) This should partition all the classes by type. Include all attributes / classes by type. Include all attributes / methods with each class, but not connectivity.methods with each class, but not connectivity.

Follow this with a fully ‘connected’ model – for Follow this with a fully ‘connected’ model – for each use case.each use case. Use those analysis classes Use those analysis classes appropriate to the use case and associate the classes.appropriate to the use case and associate the classes.

Be sure to study textbook and lectures on Be sure to study textbook and lectures on boundary, control, and entity models boundary, control, and entity models

Class structure may be realized with the Class structure may be realized with the standard standard stereotypedstereotyped classes or the RUP icons classes or the RUP icons

Page 25: Project Deliverables Version 8: 11/23/04 Final Final Version for First Semester

Guidance on Deliverable #5 Analysis Guidance on Deliverable #5 Analysis ModelModel

Remember, the validity of the model is simply Remember, the validity of the model is simply can I look at any path through a can I look at any path through a use caseuse case and see and see where/which objects will accommodate all the where/which objects will accommodate all the functionality captured in a scenario? Can it be functionality captured in a scenario? Can it be tracedtraced (with your finger...) through the objects (with your finger...) through the objects as you read through the path description? as you read through the path description?

This is the check to make! This is the check to make! VerifyVerify Traceability!!!Traceability!!! Try to cite as many attributes and methods Try to cite as many attributes and methods

(responsibilities) as possible in the respective (responsibilities) as possible in the respective class-names – boundary, control, and entity. class-names – boundary, control, and entity.

Yes, I am after associations, dependencies, etc. Yes, I am after associations, dependencies, etc. among the classes – as much as practical.among the classes – as much as practical.

Page 26: Project Deliverables Version 8: 11/23/04 Final Final Version for First Semester

Guidance on Deliverable #5 Analysis Guidance on Deliverable #5 Analysis ModelModel

For boundary to control classes, the association line is For boundary to control classes, the association line is sufficient, because it cannot be determined what method sufficient, because it cannot be determined what method in control class will be invoked from the boundary class in control class will be invoked from the boundary class unless we consider a specific scenario. Better, though, is unless we consider a specific scenario. Better, though, is a series of boundary classes constituting the interface. a series of boundary classes constituting the interface. See lecture slides for example. See lecture slides for example.

Associations among entity classes should have the Associations among entity classes should have the multiplicities, aggregations, dependencies, etc. cited, as multiplicities, aggregations, dependencies, etc. cited, as usual. They are appropriate here and may come from usual. They are appropriate here and may come from your domain model, which will VERY likely need your domain model, which will VERY likely need upgrading after/during your exercise. upgrading after/during your exercise.

BE CERTAIN to look at the slides on my web site which BE CERTAIN to look at the slides on my web site which ‘supplement’ your readings! There are many examples of ‘supplement’ your readings! There are many examples of the format you will need for the classes.the format you will need for the classes.

Page 27: Project Deliverables Version 8: 11/23/04 Final Final Version for First Semester

Guidance Deliverable 5: Non-Functional Guidance Deliverable 5: Non-Functional RequirementsRequirements

See Use Case Textbook for ‘tables’See Use Case Textbook for ‘tables’ Small systems: Small systems:

functionality; performancefunctionality; performance Large systems: Large systems:

Portability; Maintainability; Scalability; Reliability; Portability; Maintainability; Scalability; Reliability; Security Security

How about:How about: Persistence? Persistence?

Will discuss more in class; Remember the Will discuss more in class; Remember the Supplementary Specifications for Non-Supplementary Specifications for Non-Functional Requirements.Functional Requirements.

Thus the Supplementary Specifications Thus the Supplementary Specifications Document should be a Word document Document should be a Word document containing the non-functional ‘tables.’containing the non-functional ‘tables.’