DOC PREVIEW
SJSU CMPE 232 - Practice Problem (1)

This preview shows page 1 out of 2 pages.

Save
View full document
View full document
Premium Document
Do you want full access? Go Premium and unlock all 2 pages.
Access to all documents
Download any document
Ad free experience
Premium Document
Do you want full access? Go Premium and unlock all 2 pages.
Access to all documents
Download any document
Ad free experience

Unformatted text preview:

Part 1: Component-Based Software DevelopmentPart 2: Stable Pattern-Based Software DevelopmentCmpE 232 – Component-Based and Reuse-Oriented SW EngineeringPractical Problem (1)You invited a group of people for dinner. Would you think of this invitation as a modeling problem and answer the following questions?Part 1: Component-Based Software Development(1) Document two of the Use Cases in Your Problem:(a) Identify two of the use cases(b) Identify Actors and their roles(c) Identify corresponding classes(d) Describe the Use Case Repeat the process for at least two of the use cases. Use the following Use Case Template to document your Use CasesAll the fields must be filled for each use case.1. Use Case Id.2. Use Case Title3. Actors & Corresponding Roles4. Classes5. Corresponding Attributes6. Corresponding Interfaces (services or operations)7. Use Case Description – Feel free to use pre- and post-conditions where appropriate.8. Alternatives(2) Create CRC cards for at least three of the existing classes.(CRC stands for Class Responsibility and Collaborations)(3) Create a class diagram with at least 10 classes. Class diagram of your team problem based on the Traditional Model – Describe your traditional model. Class descriptions should include all attributes and methods for the class. All class relationships (associations, aggregations, dependencies, and specializations) should be included in the class diagram. Association’s classes, interface classes, constraints, interfaces, tagged values and/or stereotypes, and notes must be included in the class diagram.(4) Create Sequence diagrams. Sequence diagrams will be used to "realize" Use Cases. All Use cases should be described through sequence diagrams. The sequence diagrams can describe the same Use Cases that a flow of events was created for in the Use Case portion of the assignment.(5) Create Components diagrams for as many components in your project as you wish, and show all the interfaces, usage dependencies, ports, and connectors. Document the component diagrams. Address implementation issues that are related to these component diagrams if any.Please submit your answer electronically as MS word documents before the next lecture. – Feel free to submit all diagrams in Rational Rose or Visio formats Part 2: Stable Pattern-Based Software Development(1) Use Cases. Update #1. Fill Two (2) use case templates with software stability in mind. Use the following template to document your use cases. 1. Use Case Id.2. Use Case Title3. Actors & Corresponding Roles4. Classes1. Corresponding Attributes2. Corresponding Interfaces3. Class Classification: EBTs, BOs, IOs 4. Use Case Description6. Alternatives(2) Create or/and update all the CRC cards for all the (EBTs, BOs, Roles) in your stability model of your team project (CRC stands for Class Responsibility and Collaborations). (3) Class diagram (Stability Model). Create a new Class diagram of your team problem based on the EBTs, BOs, and IOs – Describe your stability model. Class descriptions should include all attributes and methods for the class. All class relationships (associations, aggregations, dependencies, and specializations) should be included in the class diagram. association classes, interface classes, constraints, interfaces, tagged values and/or stereotypes, and notes must be included in the class diagram. (4) Sequence diagrams. Create Sequence diagrams with stability in mind that will be used to "realize" Use Cases. All Use cases should be described through sequence diagrams. The sequence diagrams can describe the same Use Cases that a flow of events was created for in the Use Case portion of the assignment. (5) Create Components ( or Stable Patterns) diagrams based on Software Stability for as many components (Patterns) in your project as you wish, and show all the interfaces, usage dependencies, ports, and connectors. Document the component (stable pattern) diagrams. Address implementation issues that are related to these component diagrams if any. Please submit your answer electronically as MS word documents before the next lecture. – Feel free to submit all diagrams in Rational Rose or Visio


View Full Document

SJSU CMPE 232 - Practice Problem (1)

Download Practice Problem (1)
Our administrator received your request to download this document. We will send you the file to your email shortly.
Loading Unlocking...
Login

Join to view Practice Problem (1) and access 3M+ class-specific study document.

or
We will never post anything without your permission.
Don't have an account?
Sign Up

Join to view Practice Problem (1) 2 2 and access 3M+ class-specific study document.

or

By creating an account you agree to our Privacy Policy and Terms Of Use

Already a member?