1. Version Numbers will reflect added Deliverable numbers.
Project Deliverables
Version 5: 04/04/2007
Deliverable 5 Posted
Version Numbers will reflect added Deliverable numbers.

2. Overview of Guidance
I shall try to upgrade / refine guidance for each deliverable as we progress.
Please view this file often as it will change.
Suggestions for clarity and/or consistency are always welcome.

3. Format of Deliverables
All Deliverables will be via CD.
Outside: Surface of CD is to clearly indicate your course number and the team number, as CGS Team 1 or CIS 4327 – Team 1. 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.
This way, I can also see enhancements to previous deliverables.

4. Contents of Folder Each Folder (i.e., Deliverable) is to contain
Management Folder:
a number of Word files discussed ahead
Artifacts Folder
Contents discussed ahead.

5. Management Folder Documents (1 of 3)
1. Team Num file
In this file, you are to simply (may be a single Word file):
List the names of the team members
Indicate who is team leader with phone number.
Indicate who is the software quality analyst and phone
List individual accounts.
2. Iteration Plan (Include for CIS second semester deliverables)
Note that the Iteration Plan will change for each deliverable, that is, it will be refined and ‘extended.’ Each successive deliverable will contain a ‘revised’ Iteration Plan.

6. Management Folder Documents (2 of 3)
3. Executive Summary
Single page document; Summarizes the contents of this folder.
What ‘activities’ were undertaken
What ‘artifacts’ were changed and rationale
Note: revising artifacts is the norm in an iterative approach to software development.
What new ‘artifacts’ were produced
 Must include signatures of EACH team member that he/she has reviewed and has ‘bought off’ on the contents of this deliverable. (signatures may be virtual)
If you have not read and personally reviewed the contents of the deliverable, do not sign this form!

7. Management Folder Documents (3 of 3)
4. Team Activities:
Team Software Process (TSP), and
Personal Software Process (PSP) Forms
5. Software Quality Analyst Report
This will address in narrative or graphic form (your choice) the status of the project with respect to identifying and tracing requirements to date as well as efforts undertaken by you regarding testing and verification (we will discuss).

8. Artifacts Folder (1 of 2)
All developed artifacts will be found here. Sometimes the artifacts will be models; other times, they will be documents. Artifacts are sample items produced by team members as a result of undertaking specific activities.
Word documents: A project Vision Document; the Risks List; the Business Rules document, etc.
Artifact likely developed in Rational Rose: Your use-case diagrams, actors, etc.

9. Artifacts Folder (2 of 2)
Sample artifacts developed in Rose (continued):
In general, specific components of deliverables should be found here, and a number of these should be in their own subfolders, such as the user interface prototype (linked to via Rose / Requisite Pro (optional)), Use Case diagrams, Use Case Narrative, Analysis Model, Sequence Diagrams, Communications Diagrams, architectural models, etc.
We will discuss in class for each deliverable.

10. Guidance on the Rose Browser
Use Case Diagrams in Use Case Folder within Use Case Model in Rose
Capture Use Cases in separate subfolders in the Use Case folder within Use Case Model in Rose (see the Rose Browser).
Capture all Actors in folder within Use Case Model in Rose

11. Grammar and Wording
Under NO circumstances will poor grammar or ill-conceived sentences be considered acceptable work. Remember: you only get one chance to make a first impression. Poorly done work will really hurt your grade and perception of what otherwise might be high-quality work.
EACH portion of EACH deliverable should be reviewed and ‘signed off’ by EACH team member. (as stated)
This is a TEAM responsibility!!
On the provided templates, there is room for signoff by the team / team members. Use this for verification…

12. Business Modeling (Domain Analysis)
Deliverable #1
Business Modeling
(Domain Analysis)

13. Deliverable #1 Business Modeling Business Domain Analysis Due: Monday, January 29th, 2007 start of class.
Purpose:
To understand the structure and dynamics of the organization within which the application will operate;
To ensure customers, end-users, and developers understand the organization;
To derive requirements on systems to support the organization;

14. Deliverable 1 – Business Model Domain Analysis Deliverable Artifacts
Business Vision Document - a text document.
Business Use Case Model – captured in a Rational Rose model
Business Glossary - text
Business Rules – text
Business Risk List - text
(Domain Model - model in Rational Rose – will accommodated in Deliverable #2.)
This is a hefty assignment. Start early!!

15. Deliverable #1: Business Vision Document (1 of 2)
Use the appropriate forms available at:
RUP document templates are located at the site See also my web page.
This captures (Word document) the purpose of the business enterprise.
What services are they providing?
What are they all about?
Who are the customers?
What are the goals of the business?
Primary stakeholders??
This is NOT a product vision document (the product you will develop). This is about the business, enterprise, environment.)

16. Business Vision Document (2 of 2)
You may use the Vision Template (see web page) but you must MODIFY it so that it does NOT address a project; rather, it will capture the vision of the enterprise itself.
Eliminate section 2. Elaborate on section 1. In Stakeholders, address those interests NOT from a project perspective but from an organization’s perspective: customers, users, etc. There is no Product Overview But your business vision document should address what the business is all about. Add major sections that you deem appropriate.
This is a template. It offers organization, but it need to be rigidly adhered to.

17. Deliverable #1: Business Use Case Model (1 of 2)
Simple in structure . See pp in the RUP textbook.
You only need show the Model (with actor and business use case icon) (top part of figure 8.5) (Single page)
You do NOT have to display the Use Case specification.
Each use case is identified and actors who interact with this and each business use case.
A Business Use Case Diagram (the top part of figure 8-5) is developed in verb…object format and captured in Rose.
All major use cases and actors should be captured in this business model.
See link to sample on my web page.
Note: Develop this artifact in the Use Case View, Business Use Case Model in the Rational Rose Browser.

18. The Business Use Case Model (2 of 2)
When logging onto Rose, be sure to select RUP icon from the initial window.
Be also certain to notice the tool mentors – when you select a folder in the Rose Browser, a description often appears with invaluable information.
The Business Use Case Model must be developed in the Use Case View (see last slide)
This is a single model of the key business processes of the organization.

19. Deliverable #1: Business Glossary (1 of 2)
Definitions of important terms used in the business. (alphabetical)
Key words: (sometimes these are called
‘core abstractions.’ ) These are often the ‘things’ the business deals with. Business Entities.
A Student Registration system might have key words like Course, Schedule, Payment, Registration, Student, Professor, ….
What is needed here are acronyms, important definitions, basically the jargon of the organization. These will be heavily referred to when we do use cases!

20. Deliverable #1: Business Glossary (1 of 2)
Another key component of domain analysis is the domain model (next deliverable). Here, we supplement the glossary by adding in a graphical mode – business entities, their relationships and associations:
(What’s important in business entities are the ‘attributes.’ So, for example, if you were defining a Student business entity, you might include things like: ssan, classification, gender, major, gpa, projected graduation date, ACT/SAT scores, etc.
We do NOT worry about methods (operations here)
This, however, is for the next deliverable.)

21. Deliverable #1: The Business Rules
Use the appropriate forms available at:
RUP document templates are located at the site See also my web page.
The link for the Business Rules template is incorrect (points to the Business Modeling Guidelines template), so there is another link to point to the Business Rules format.
See examples on my web page. These are merely samples.
Be careful: The samples on my web page are Rules for an application that will be developed (later). Your Rules are simply for the organization itself - the way it does business; guiding principles. It has no relationship (at this time) to an application to be developed.
Business Rules are policy declarations or conditions or guidelines that must be satisfied in running the business.

22. Deliverable #1: The Business Risks List
Very general at this stage.
What are some of the risks that the organization must be constantly assessing:
e.g. market share, technology awareness, new statutes from Washington D.C., trends in the industry; demographics; environmental considerations, maintaining top notch software developers, keeping developers current; training; give this some thought….
Again, this is at the organizational level.
That’s it! Have fun!

23. Domain Model The Product Vision Document Statement of Work
Deliverable #2
Domain Model
The Product Vision Document Statement of Work

24. Deliverable #2 – Artifacts Due: Monday, Feb 14th
1. Build a Domain Model (precursor activity to Use Case development)
Is an essential activity to facilitate good use case development that contains glossary items and objects from the problem space (domain).
2. Build a Product Vision Document
Will include User Needs and Features
3. Develop a Statement of Work – assigning responsibilities to different roles to be accommodated on the team.
Review / upgrade previous artifacts.
Business Use Case Model, Use Cases and Actors - Modeled
Business Vision document – text, Business Glossary - text
Business Rules - text

25. Deliverable #2: Domain Model
1. Domain Model – The Domain Model should be captured as a separate folder under the Logical View in your Rose Browser.
This is a major effort that takes into consideration attributes, multiplicities, associations, etc.
Be careful. the Domain Model may look like a Database Schema. It isn’t. It is similar – to a degree – to a Fully Attributed List in the Logical Model – but there are differences.
Notice also – a good domain model does not have methods – only attributes and connections (associations/ dependencies)
There is a decent link to a student example on my web page. Notice it is found in the Logical View (as it should).

26. Domain Model - continued
Is a continuation of Domain Analysis…
The Domain Model is an extension of Deliverable 1. It deals with the entities in the organization itself.
Domain Model is essential to understanding the environment within which the application to be developed will function.
It is sometimes the only item from the Business Case. But it is an essential artifact.
 See Lecture 8 on the Domain Model.

27. Deliverable #2: Product Vision Document
This represents the vision for the application you will be developing. This essential artifact is called the Product Vision Document.
Use the template provided.
In my webpage, take the link to the RUP documents and access the Project Management Templates : Product Vision Document.
You may transfer much of the information from the Business Vision Document to this Product Vision Document.
You are to add the Problem Statements (section 2.2) and all the other items dealing with the Stakeholder and User Profiles and Stakeholder and User Needs.
You need not include the Product Overview section.
Product Features Section (section 5) is essential and is to include identification of stakeholder needs and their mapping to features via the traceability matrix shown in lecture materials.

28. More on Needs and Features
When we are dealing with ‘needs’ and ‘features’ we are dealing with reasonably high levels of abstraction.
But it is critical to capture the features in the Vision Document for a new application, because it is these features that must be accommodated in the delivered system.
The ‘Features’ drive the development of the use cases – our functional requirements, and the development of our supplementary specifications – our non-functional requirements.

29. More on Sample Features
Features are not behavioral (like the Use Cases). These are typically text descriptions. (Use Cases (later) are behavioral)
Example of features: (We will discuss)
ClassicsCD.com Web Shop Need a Secure payment method. There must be easy browsing for available titles. Users need the ability to check the status of an order. Application must provide Customer notification. The catalog shall be highly scaleable to include many titles and effective searching through those titles. The Customer shall be able to customize the Web site. The Customer shall be able to register as a user for future purchases without needing to re-enter personal information.

30. Deliverable #2: Statement of Work
My take on this is a bit different than the Use Case Book. It should be a Word document. See textbook and/or templates for format
What is your team plan?
Meetings/ (see forms on web page)
Who does what (that is assign roles)?
What are the responsibilities that must be fulfilled by each role?
What is your plan? (See textbook)
This short document should appear in the Artifacts Folder

31. Deliverable #3 Use Case - Façade Iteration and Initial User Interface Prototype
due: Monday, March 5th, 2007

32. Use Case - Façade Iteration plus Initial User Interface Prototype
Executive Summary (overviews new artifacts and ALL changes/revisions to existing artifacts, such as the revised Iteration Plan, etc. as required.
Specific Work:
Revisit the Business Case (Deliverables 1 and 2) including artifacts listed below and update them. (Risks Lists; Business Rules; especially the Domain Model; Statement of Work, etc.)
Include an index (numbered) for Use Cases that follow. (see example on my web page)
Use Case Index is to contain a number, Use Case name, short description, and other high level items you consider important. Construct this in tabular form using a table in Word. See power point slides for detailed attributes needed. See examples on web page too.

33. Guidance on Façade Iteration
Develop an overall Use Case Model (Diagram) (all application Use Cases and Actors). Similar to Business Use Case Model.
Develop Façade Use Case Descriptions and associated Use Case Diagrams for each Use Case. (See my web page)
Use Rose (Use Case View) for your models. Link the Use Case Narrative (use case specification) text and ensure these descriptions are on the CD you turn in for grading.
Model your Façade Use Cases using the Kulak and Guiney book. Again, see power point lectures for required attributes. See examples of ‘reasonable’ student Use Cases examples posted on my web page. (Façade do not contain basic courses of events and alternatives / exceptions)
Additional information: Visual Modeling book and Rose Basics (see power point lecture slides for examples on including your Use Cases in your Rose Model in the Use Case View.)

34. Guidance on: Facade Iteration
Remember that the Façade iteration names the use case, identifies actors, provides a short description, frequently includes pre- and post conditions, triggers, etc. But it does NOT include the detailed actor-system interactions.
See lecture notes for required attributes.
Must include all Use Cases.
Include your single Use Case Model in the Use Case View (in Rose) in the folder provided by Rose. Note: this is NOT the Business Use Case Model, which has been completed; more, the icons are different for the actors and use cases. Be sure to note the differences.
Do not include Activity Diagrams in this deliverable.

35. Guidance on User Interface Prototype
Develop User Interface Prototype…needed for requirements capture!!! Iterate this as needed. (Should be done in conjunction with the Façade Use Case and will (together with Domain Model) greatly assist you for Deliverable #4, your full-blown Use Case Descriptions with alternate and exception paths.
You may use any prototyping tool you wish: VB, Javascript, etc. Your prototype should include storyboarding.
Most teams use static html; some use Front Page; some contain Javascript, etc.
To accompany the Façade Use Cases, user interface prototype needs to be total complete. While we are not including actor – application ‘interchanges,’ these are essential for the next deliverable.
See examples of initial user interface prototypes on my web page.
See also (ahead) lecture slides on User Interface Design

36. Deliverable #4 Develop a System Level Use-Case Diagram
Develop Full/Mature Use Case Specifications
Develop Activity Diagram for each Use Case
Revisit and Revise:
Domain Model,
Façade Use Case Specifications and Diagrams
User Interface Prototpe
All Management Docs

37. Deliverable #4 Overview due: Wednesday, March 28th ,2007
Executive Summary; Cite all revisions and overview activities.
System-Level Use-Case Diagram – a single sheet (hopefully) that shows all use-cases in a ‘center column’ with actors to the left and right of the use-cases with their appropriate connections. We can discuss in class.
Develop Mature Use Case Specifications and the associated Use Case Diagram for each Use Case.
Show include or extend use-cases where appropriate (if used)
Each Use Case is to be accompanied by an Activity Diagram that should indicate flow for all paths in the Use Case
Please ensure (I want you to certify this…) that there are at least two of you undertaking the Rose Modeling.
Revisit the Domain Model for added / altered business entities; revisit your Risks document, Business Rules, and Product Vision statement.
These changes may have become apparent based on your development of your mature use-case specifications.
If you change these documents, please site the changes in your Executive Summary.
Upon ‘completion’ of Use Case specifications, revisit the UI. It is very likely you will have changes here. If so, cite in Executive Summary.

38. Use Case Specifications
System Level Use Case Diagram: Develop a single Use Case Diagram for the entire Application too. This will be a single diagram containing all actors and all use cases and connections.
Complete Use Case Specification and Use Case Diagrams. For each Use Case develop these artifacts.
This is a major assignment. I anticipate a major presentation on this deliverable.
Complete your model by including alternative, exception flows, and ‘sub-flows’, using extension points or other tags as appropriate. Ensure these are complete.
Now that you are supplying the text of actor – system interchanges, it is quite likely you will have include and extend use-cases. Be certain to separately document them in your use-case index and additional use-cases as needed. (I would be amazed if there aren’t any.)

39. Use Case Specifications - More
Allocate functional requirements / features to use cases via the stories of interactions.
This is a painstaking and arduous task! It will underpin almost all of your remaining work. Spend time here!!!! Recognize that Use Cases are NOT functional requirements in themselves; rather, they are stories of actor-application interactions which contain the required functionality.
Try to get the proper level of granularity. (Discussed in class).
All customer functionality should be accounted for here.
Be certain to use your Domain Model and italicize or bold all references to entities in the domain model and/or Glossary.
Ensure everything the customer desires is accounted for!
 Iterate and reiterate the Use Case Model. Review, Review, Review!

40. Rational Rose Modeling Use-Case View
In Rose, put Use Cases into packages appropriate to the major feature(s) and groupings of features they address.
(These may assist in our software architecture later – as these may become likely subsystems).
Use Rose (Use Case View)
Kulak and Guiney book (Use Cases); Visual Modeling book and Rose Basics (see power point lecture slides for examples.)
Recognize that Use Cases are really never ‘finished.’ They become more ‘mature’ as we learn more.

41. Activity Diagrams Develop one activity diagram per Use Case.
Activity Diagrams include all alternate / exception paths.
You may view an Activity Diagram as a visual model of the Use Case, since it will contain all scenarios.
Include Activity Diagrams in a separate package in Rose Browser in the Use Case View under Use Case Models in a folder entitled Activity Diagrams.
See Visual Modeling text for examples and use Rose.

42. Revisiting / Iterating Previous Deliverables Special emphasis: UI and Domain Model
Be absolutely certain to revisit / modify your User Interface Prototype in light of the development of the collection of Use Cases. Recognize this collection represents the functionality of the application.
Ask yourselves if the Use Case specifications support these major functions at a sufficient level of granularity to support design, testing, architecture development, etc.
The most major options presented on the UI must reflect the most major features to be implemented – up front…

43. This will be a major milestone in our development efforts.
Once we can ‘baseline’ these artifacts with user concurrence,
we will then embark upon Analysis Modeling
Please also note that this deliverable involves considerable work
with Rose modeling. Be certain to share this workload equally
among the team members and let me know who has
responsibility for what activities in your Executive Summary.
This is not a deliverable that can be easily split across four or
five people. You will need to work together on these.

44. Deliverable 5 Task 1: Analysis Model and
Task 2: Non-Functional Requirements
Due: 2/23/2007

45. Task 1: Analysis Modeling
Analysis Model (Preliminary Design)
Contains communicating boundary, control, entity objects with relationships
 Will flow from your use case narratives and prototype
Supports Interaction Modeling and much more…
Designed to lead ultimately to the class model (static)
Sources: Use your prototype (boundary) again, domain model (entities), and use case descriptions (boundary, control, and entity objects) in earnest. They may not be enough, but will help. See also your Vision Document.
See Visual Modeling Book; RUP; Logical View on Rose

46. Guidance on Deliverable #5 Analysis Model - 1
Static Model:
Include boundary classes together, control classes together, and entity classes together all without associations to other classes. (a one-page drawing) This should partition all the classes by type. Include all attributes / methods with each class, but not connectivity. (See textbook for sample rendering)
Follow this with a fully ‘connected’ model – for each use case.
Be sure to study textbook and lectures on boundary, control, and entity models
Class structure may be realized with the standard stereotyped classes or the RUP icons

47. Guidance on Deliverable #5 Analysis Model - 2
Dynamic Model – Interaction Diagrams
For each Use Case Do:
One sequence diagram for the happy path.
IF by chance your happy path is very short, you must alternatively model a path with more detail (objects) in it.
You may also be able to include alternate paths / exception paths on this single drawing.
You are to include your use-case specification text down the left boundary of the sequence diagram page. This will serve as a check on this realization of the narrative.
Clearly, this must be done in Rose.
Also include collaboration diagrams (now called communication diagrams). You only need toggle F5.
These models will be in packages in the Logical Model
Access samples of student work for additional examples.

48. Additional Guidance on Deliverable #5
Remember, the validity of the analysis modeling is simply can I look at any path through a use case and see where/which objects will accommodate all the functionality captured in a scenario? Can it be traced (with your finger...) through the objects as you read through the path description?
This is the check to make! Verify Traceability!!!
Try to cite as many attributes and methods (responsibilities) as possible in the respective class-names – boundary, control, and entity.
Yes, I am after associations, dependencies, etc. among the classes – as much as practical.

49. Additional Guidance on Deliverable #5
For boundary to control classes, the association line is sufficient, because it cannot be determined what method in control class will be invoked from the boundary class unless we consider a specific scenario. Better, though, is a series of boundary classes constituting the interface. See lecture slides for example.
Associations among entity classes should have the multiplicities, aggregations, dependencies, etc. cited, as usual. They are appropriate here and may come from your domain model, which will VERY likely need upgrading after/during your exercise.
BE CERTAIN to look at the slides on my web site which ‘supplement’ your readings! There are many examples of the format you will need for the classes.

50. Task 2: Non-Functional Requirements
See Use Case Textbook for ‘table’ examples.
Small systems:
functionality; performance
Large systems:
Portability; Maintainability; Scalability; Reliability; Security
How about:
Persistence?
Will discuss more in class; Remember the Supplementary Specifications for Non-Functional Requirements.
Thus the Supplementary Specifications Document should be a Word document containing the non-functional ‘tables.’
Do not take this part of the deliverable lightly. It is essential to follow-on design.

51. The End is in Sight!
This is a major deliverable, especially in lieu of the very high granularity of your use-cases. It is VERY likely that your use-cases may need significant revisiting to drill down to lower levels.
This may well be true to support a more comprehensive deliverable #4 but to serve as primary input to deliverable #5. I’d start with your use-cases…
I strongly urge you to jump on this one. You have three weeks, which is a lot of time. But there is a lot of work to be done.
I strongly suspect that you will need to work physically together to drill down in your use-cases – your primary input to ‘this’ deliverable. There is a ton of work to be done but the opportunities to learn this process is super!
Do NOT hesitate to come and see me along the way!
There is much to be learned, especially in analysis modeling, interaction diagramming in Rose. These are hugely marketable skills. Please share as equally as possible in these deliverables.