CIS608                                                    Assignment 2
Due 10/31/2006

Part I:

Develop a business information system use-case model using UML. You can either use IBM Rational Rose or Software Architect to specify the system requirements and models.

1. Develop the Use-Case diagrams (actors extend and include associations)

Use-case diagrams present a high-level view of your system usage as viewed from an outsider’s (actor’s) perspective. These diagrams should show the functionality of your system and how your system interacts with the outside world.

 

2. Develop the Sequence diagrams

A sequence diagram illustrates object interactions arranged in a time sequence.  These diagrams are typically associated with use cases. Sequence diagrams should show you step-by-step what has to happen to accomplish something in your use case. This type of diagram emphasizes the sequence of events,

 

3. Develop the Collaboration diagrams

Collaboration diagrams provide a view of the interactions or structural relationships between objects. This type of diagram emphasizes the sequence of events,

 

4. Develop the Activity diagrams (Start and end state, Activities, Transitions, Decisions, and Synchronization-bar.)

Activity diagrams model the workflow of a business process and the sequence of activities in a process. These diagrams are very similar to a flowchart because you can model a workflow from activity to activity or from activity to state. It is beneficial to create an activity diagram early in your modeling of a process to help you understand the overall process.

Part II:

1. Write a MS Word report that describes your development process (list the major steps of development) and your business information system model (screen shots). Email me the report before the due day.

2. Demo your business information system model using the IBM rational software to the class on the due day.

Good models:

·       Identify requirements and communicate information

·       Focus on how system components interact, without getting bogged down in specific details

·       Allow you to see relationships among design components     

·       Improve communication across your team through the use of a common, graphical language.