Analysis Work Flow: Osric Company (Term Paper Sample)
Determine use cases and descriptions, scenarios, classes, attributes for entity classes, dynamic model of the information system, class diagrams for use cases, collaboration and sequence diagrams for scenarios, flow of events statements, and the overall class diagram (See attachement for full instructions) Here is the link where you can download the textbook: http://f3.tiera.ru/2/Cs_Computer%20science/CsPl_Programming%20languages/Schach%20S.%20Object-Oriented%20Software%20Engineering%20(7ed.,%20MGH,%202007)(ISBN%20007352333X)(O)(578s)_CsPl_.pdf I don’t need introduction, case description and all such introduction staff. I will need a Functional Decomposition Diagram as a start, then all uses cases – my recommendation are 1. Acceptance 2. Service Request Management 3. Manage a Job (Processing) and 4 Billing. So we will have 4 use cases. Then you should go for rest of the instruction from attachment. I don’t need nice looking diagram, just a clear solutions. I need the job to be concentrate more on the Service Request Use Case, for the rest just the diagrams is enough.
source..Analysis Work Flow
Student Name
Institution
Analysis workflow for the Osric Company
This is the analysis workflow of a software product that is to be constructed for the Osric Company to use in performing data processing and also used in responding to telecommunication service requests. In particular, the product will be in a position to assign technicians to the request for service from customers. The system should also be in a position to generate bills and print various reports regarding the requests made, waiting lists and the outstanding jobs.
Functional Decomposition Diagram
FDD below shows the Osric Company case study (Figure 1 was drawn using EdrawMax open source software).
Use Cases
1 Use case for Acceptance
The use cases exhibited in this scenario includes;
* Client makes a call to request for a service
* Assistant takes up the call
* Assistant request for the company number or name
* Client gives out company’s number or name
* Assistant adds the request to the waiting list
Use case diagram to show the above use case scenario is as shown in figure 2 below (Figure was drawn using EdrawMax open source software).
A class diagram for the realization and detailed system explanation of the scenario above (acceptance use case) is as shown in figure 3 below.
A communication diagram for the realization and detailed system explanation of the scenario above (acceptance use case) is as shown in figure 4 below.
A sequence diagram for the realization and detailed system explanation of the scenario above (acceptance use case) is as shown in figure 5 below.
2 Use case for Service request
The use cases exhibited in this scenario includes;
* Assistant add job to the waiting list
* Assistant then assigns the newly added job to the technician
* Technician then handles the task
* Assistant checks the task if completed on time, if not, calls the customer to extend the time to handle the task
Use case diagram to show the above use case scenario is as shown in figure 6 below (Figure was drawn using EdrawMax open source software).
A class diagram for the realization and detailed system explanation of the scenario above (use case for Service request) is as shown in figure 7 below.
A communication diagram for the realization and detailed system explanation of the scenario above (service request use case) is as shown in figure 8 below.
A sequence diagram for the realization and detailed system explanation of the scenario above (service request use case) is as shown in figure 9 below.
3 Use case for Manage job (Processing)
The use cases exhibited in this scenario includes;
* Assistant add job to the waiting list
* Assistant then assigns the newly added job to the technician
* Technician then records the task information in a card
* Technician hands over the card to the Assistant.
Use case diagram to show the above use case scenario is as shown in figure 10 below (Figure was drawn using EdrawMax open source software).
A class diagram for the realization and detailed system explanation of the scenario above (manage job use case) is as shown in figure 11 below.
A communication diagram for the realization and detailed system explanation of the scenario above (manage job use case) is as shown in figure 12 below.
A sequence diagram for the realization and detailed system explanation of the scenario above (manage job use case) is as shown in figure 13 below.
4 Use case for Billing
The use cases exhibited in this scenario includes;
* Assistant feeds the card information about the task into the system.
* Assistant then process the billing information according to the task time taken to process
* Assistant then generates billing reports of respective clie...
Other Topics:
- Software Development Life Cycle Models: Applications, Advantages and DisadvantagesDescription: Compare between the different types of Software Development Life Cycle Models and specify the applications and projects that would be suitable ...8 pages/≈2200 words| 4 Sources | Other | Technology | Term Paper |