DOC PREVIEW
SJSU CMPE 133 - 15-ASRMS-PP-15

This preview shows page 1-2-3-4 out of 11 pages.

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

Unformatted text preview:

Software System EngineeringCmpE 202 Practice Problems1. INTRODUCTION2. MOTIVATION3. DESIRED ASRMS4. SYSTEM COMPONENTS4.1 Composite Status Reporting Interface (CSRI)4.2 Data Structuring Component (DSC)4.3 Intelligent Presentation Component (IPC)4.3 Request-Response Handler (RRI)4.4 Report Generation Interface (RGI)5. DETAILED REQUIREMENTS6. USE CASES6.1 LoginRole in Context: To enable user login6.2 CSRI Status EntryRole in Context: Users enter their status through CSRI6.3 Storing the Form DataRole in Context: Stores status data in a corresponding database6.4 Generate XML Data from the DatabaseRole in Context: Generation of structured data by DSC6.5 Transform XML DataRole in Context: Transforming the XML data for customization6.6 Get Device CapabilityRole in Context: Retriever of information about remote device capability and preferences6.7 Process Remote RequestsRole in Context: Process ASRMS remote server requests6.8 View Status ReportsRole in Context: Generate and view status reports6.9 Analyze Graphical ReportsRole in Context: Ability to graphically analyze status information6.10 Track Project StatusRole in Context: View project details for an existing project6.11 Backtrack EmployeeRole in Context: Generate employee status details for a period of time6.12 Compare Status ReportsRole in Context: Compare the current status report with past reports6.13 Identify RisksRole in Context: To identify and forecast major risks for a project6.14 Risk Analysis ComparisonRole in Context: To compare the risk analysis performed with the preset company metrics6.15 Manage attachmentsRole in Context: Manage the attachments associated with employee statuses6.16 Retrieve Custom DataRole in Context: To retrieve and present user specified data6.17 Generate LogsRole in Context: Generate classified logsDescription: Logs are generated and classified based on the user actions. Separate logs are generated for actions relating to status report comparison, risk evaluation, backtracking, and the processing of remote requests.7. ARCHITECTURE8. GLOSSARY9. REFERENCESSoftware System EngineeringCmpE 202 Practice Problems Practice Problem (15)Automated Status Report Management System_________________________________________________________________________Read the following problem statement and perform the following:1. Use Case Diagrams and Use Cases. Use one or more diagrams to describe all the actors in design session problem and how they will interact with the Use Cases of your system. Provide Flow of Events for all of your Use Cases. Use associations, aggregations, and generalization in the use case diagram(s) and don’t forget to use multiplicities. Use case diagram(s) textual description is a must. Use the following template to document your use cases. 1. Use Case Id.2. Use Case Title3. Actors & Corresponding Roles4. Corresponding Classes5. Corresponding Attributes6. Corresponding Interfaces(7. Class Classification: EBTs, Business Objects, and Industrial Objects for softwarestability model)8. Use Case Description9. AlternativesEvaluation: Use the model essentials to evaluate the use case models.2. Document all the CRC cards for all the (classes) classes in the design session problems (CRC stands for Class Responsibility and Collaborations)Class Name (Role)Collaborations1Responsibility Clients Servers Evaluation: Use the model essentials to evaluate the CRC cards.3. Class diagram (Traditional Model). Create a class diagram of the design session problems based on the Traditional Model. Class diagram 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.Evaluation: Use the model essentials to evaluate the class diagram (Traditional).4. 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. Evaluation: Use the model essentials to evaluate the sequence diagrams.5. Activity Diagram. Activity diagram is similar to procedural flow charts except that all activities are uniquely associated with objects. Activity diagrams support the description of parallel activities. Activity diagrams: (a) Describes how activities are coordinated; (b) Is particularly useful when you know that an operation has to achieve a number of different things, and you want to model what the essential dependencies between them are, before you decide in what order to do them; (c) Records the dependencies between activities, such as which things can happen in parallel and what must be finished before something else can start; and (4) Represents the workflow of the process. Activities, transitions, decision diamond, constraints, synchronization and splitting bars, boundaries, and start & stop markers must be included in the class diagram. Evaluation: Use the model essentials to evaluate the Activity diagrams.Iterate: Redo 1, 2, 5, and 6 with stability in mind where:Class diagram (Stability Model). Create a new Class diagram of the design session problems based on the EBTs, BOs, and IOs. Class model should include all attributes and methods for the class. All class 2relationships (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.Evaluation: Use the model essentials to evaluate the class diagram (Stability Model)._________________________________________________________________________Automated Status Report Management SystemAbstractA status report is a way to convey the details of the work done during a particular period of time. In abusiness context, it helps to keep track of employee time and progress on the tasks assigned to them.Conventional status reports in a corporate environment are text documents with a defined format that aresent to the manager and/or team leader. It takes additional effort to create, edit, store and retrieveinformation using these text documents. ASRMS is intended to automate this process by


View Full Document

SJSU CMPE 133 - 15-ASRMS-PP-15

Download 15-ASRMS-PP-15
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 15-ASRMS-PP-15 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 15-ASRMS-PP-15 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?