The document provides a case study for a software engineering midterm assignment on software requirements specification and design. It includes questions to analyze requirements for a defect tracking system, draw a use case diagram, activity diagram, and class diagram for the system. The assignment is due on April 13, 2020 and must be submitted to the specified instructor and include the student's registration number. Late submissions will not be accepted.
The document provides a case study for a software engineering midterm assignment on software requirements specification and design. It includes questions to analyze requirements for a defect tracking system, draw a use case diagram, activity diagram, and class diagram for the system. The assignment is due on April 13, 2020 and must be submitted to the specified instructor and include the student's registration number. Late submissions will not be accepted.
The document provides a case study for a software engineering midterm assignment on software requirements specification and design. It includes questions to analyze requirements for a defect tracking system, draw a use case diagram, activity diagram, and class diagram for the system. The assignment is due on April 13, 2020 and must be submitted to the specified instructor and include the student's registration number. Late submissions will not be accepted.
The document provides a case study for a software engineering midterm assignment on software requirements specification and design. It includes questions to analyze requirements for a defect tracking system, draw a use case diagram, activity diagram, and class diagram for the system. The assignment is due on April 13, 2020 and must be submitted to the specified instructor and include the student's registration number. Late submissions will not be accepted.
Shaheed Zulfikar Ali Bhutto Institute of Science & Technology
COMPUTER SCIENCE DEPARTMENT
Instructions: Copied or shown assignments will be marked zero. Late submissions are not entertained in any case.
Attempt all questions:
Q1: Read the following case study IBM Rational Clear Quest: (3.75 marks) A reputable software company just switched to Mac desktop. We want to build a new web-based CASE Tool which should be able to help a software engineering in throughout SDLC process to manage software defects. In this tool when we add new defect into system by creating a ticket and a ticket could be for new issue or an existing issue. And if that issue is too old to trace, we can certainly reproduce an issue and assign to different developer to solve it. Usually regular tickets go to their creator only. Issue could be requirement base as well. If the issue gets fixed by creators, they can change its status “ready to test” and assign back to their originator. Which can check it again if he found it satisfactory, he close ticket or else re-assign back to its creator. During this whole process one person PM can look the whole process, and send messages(private messages) to each person to find out issue that cause delays in that process but that thing can delay. A. For the above given case study specify if the requirement is Unambiguous, Complete, consistent and verifiable? Answer: The above given case study specifies that requirement is an unambiguous because: It is not well-known as assigning the new tickets for the same reason to the same persons just because the reported problem is not solved yet will make the system overload and complex and also can result in errors that will affect the performance of the system. But the requirements are complete and we have the advantage because it is giving us a clear vision of how the system is intended to work while we can make requirements even better by user different elicitation techniques. Waterfall Model will prove best for this purpose. Because the company switched its system to Mac desktop. We have all the thing that we needed to switch like requirements are all well-known already. Waterfall Model is the simple and most effective when we have requirements well-known for developing the product of the organization.
Software Engineering (LAb) BSCS-5 SZABIST-ISB
Shaheed Zulfikar Ali Bhutto Institute of Science & Technology
COMPUTER SCIENCE DEPARTMENT
B. Rank the important modules.
Answer: Modules: 1. User module Get the Information 2. Creator module Assign the ticket to developer Check the ticket Test the ticket 3. Admin module Status of the progress Reporting section Private messages
C. Write the functional and non-functional requirements
Answer: Non-Functional requirements: 1. System should be simple and easy to use by the customers. 2. It helps you to ensure good user experience and ease of operating the software. 3. It must ensure the software system follow legal and compliance rules. 4. The software should be portable. So, moving from one OS to other OS does not create any problem. 5. In case of error proper message displayed. Functional requirement: 1. Employee of the company will operate the system. 2. It should take the customer information for assigning the tickets like name, ID card number, and phone no, address etc. 3. Generate a ticket with serial number. 4. The customer will be assigned to a specific developer. 5. They will come according to the ticket number. 6. Each customer must have ticket. 7. Progress bar display where the currently working project status will be uploaded. 8. PM will get a report of every project. 9. There should be a quality check and testing of the project.
Software Engineering (LAb) BSCS-5 SZABIST-ISB
Shaheed Zulfikar Ali Bhutto Institute of Science & Technology
COMPUTER SCIENCE DEPARTMENT
Q2: Draw Use case Diagram for the case study given above. (3.75 marks) Answer: The actors in this case study are: Employee Customer Developer PM
1. Employee:
Use Case 1 ID: Use Case Employee Name: Created IBM Rational Clear Quest By: Date April 04, 2020 Created:
Software Engineering (LAb) BSCS-5 SZABIST-ISB
Shaheed Zulfikar Ali Bhutto Institute of Science & Technology
COMPUTER SCIENCE DEPARTMENT
2. Customer:
Use Case 2 ID: Use Case Customer Name: Created IBM Rational Clear Quest By: Date April 04, 2020 Created:
Software Engineering (LAb) BSCS-5 SZABIST-ISB
Shaheed Zulfikar Ali Bhutto Institute of Science & Technology
COMPUTER SCIENCE DEPARTMENT
3. DEVELOPER:
Use Case 3 ID: Use Case DEVELOPER Name: Created IBM Rational Clear Quest By: Date April 04, 2020 Created:
4. PM:
Software Engineering (LAb) BSCS-5 SZABIST-ISB
Shaheed Zulfikar Ali Bhutto Institute of Science & Technology
COMPUTER SCIENCE DEPARTMENT
Use Case 4 ID: Use Case Program Manager Name: Created IBM Rational Clear Quest By: Date April 04, 2020 Created:
Actors: Employee, Customer, Developer, PM
Description: This system is basically IBM Rational Clear Quest and it has the actors given above. Each has its own different functionality. Trigger: System triggers whenever a new ticket is generated. Preconditions: There should be some ticket Postconditions: Issues are resolved so that ticket could be returned to the creator Normal Flow: When a creator generates a ticket normally the system starts Sunny Day Scenario: working.
Alternative Flows: If the previously generated tickets are still on pending then Rainy Day Scenario: different developers are required to resolve the issues
Software Engineering (LAb) BSCS-5 SZABIST-ISB
Shaheed Zulfikar Ali Bhutto Institute of Science & Technology
COMPUTER SCIENCE DEPARTMENT
Q3: Draw Activity Diagram for the case study given below. (3.75 marks) An online document management system works as follows, the user creates the document and reviewer performs review and approves the documents. If the document gets approved it is achieved in database and make visible online and if document didn’t get approved it is updated and again reviewed and approved. Activity Diagram (online Document Management System)
Software Engineering (LAb) BSCS-5 SZABIST-ISB
Shaheed Zulfikar Ali Bhutto Institute of Science & Technology
COMPUTER SCIENCE DEPARTMENT
Q4: Draw Class Diagram for the case study given below. (3.75 marks) Construct a design element for Point of sale terminal management system that can be used for buying and selling of goods in the retail shop. When the customer arrives at the post check point with the items to purchase. The cashier records each item, price and adds the item information to the running sales transaction. The description and price of the current item are displayed. On completion of the item entry the cashier informs the sales total and tax to the customer. The customer chooses payment type (cash, cheque, credit or debit).After the payment is made the system generates a receipt and automatically updates the inventory. The cashier handovers the receipt to the customer.
Microsoft Power Platform Up and Running: Learn to Analyze Data, Create Solutions, Automate Processes, and Develop Virtual Agents with Low Code Programming (English Edition)
Microsoft Power Platform Up and Running: Learn to Analyze Data, Create Solutions, Automate Processes, and Develop Virtual Agents with Low Code Programming (English Edition)
