LAB-#01

.pdf

School

Carleton University *

*We aren’t endorsed by this school

Course

3120

Subject

Industrial Engineering

Date

Dec 6, 2023

Type

pdf

Pages

4

Uploaded by ColonelSnailMaster972

SYSC 3120: Software Requirements Engineering Lab Assignment #01 Fall 2023 Dr. N. Kahani Carleton University Department of Systems and Computer Engineering Posted: September 11, 2023 Due: September 11, 2023 This lab assignment contains 4 pages (including this cover page) and 5 problems. You are responsible for ensuring that your copy of the assignment is complete. Bring any discrepancy to the attention of your instructor/TA. This lab assignment will not be graded. However, you should make reasonable progress towards completing the activity. THIS LAB ASSIGNMENT WILL BE GRADED AS SAT/USAT Page 1 of 4
SYSC 3120 — Lab Assignment #01 Due Date: September 11, 2023 The purpose of this lab assignment is to exercise your understanding of functional and non-functional requirements and writing high-quality requirements. It aims to assess your ability to identify and explain the different types of requirements and to document high-quality requirements that describe the visible behaviour of a software system. The following example system, which describes an issue tracking system for a software company, illustrates the kind of informal specifications that a software or systems engineer must translate into a computable form. Note that the IssueTracker , described below, is simplified significantly for this assignment. IssueTracker: An Issue Tracking System for a Software Company A software company (MicroComp) is looking to develop and adopt an issue tracking system to allow its clients to report technical issues with the company’s software products and get required help to resolve the issues. A resolution for an issue can range from a simple technical answer to a complex software patch that involves many changes. Currently, MicroComp uses email communications to provide technical support, i.e., clients send emails to the support’s email address (support@microcomp.com). This method was working at the beginning, when the number of clients was low. However, due to the recent growth in the number of products and clients, it is getting more and more difficult to provide proper support services to the clients, and the MicroComp management is concerned that this situation could cause clients’ dissatisfaction and ultimately lead to business loss. Also, it is almost impossible to monitor products’ issues and related workloads to address the issues, which are critical to provide and plan for proper client support. To solve the mentioned problems, the company has decided to develop a new issue tracking system, called IssueTracker , to enable clients to report their technical issues with MicroComp products, to enable MicroComp staff to view the issues, to have technical experts assigned to the issues, and to ensure that all clients’ requests are addressed quickly. The proposed system would need to interface with the client management system to be able to determine if a client is eligible to report an issue for a certain product, and to ensure that the valid support requests are handled based on the existing service level agreements (SLAs) with the clients. It also should be integrated with the existing software release management system at MicroComp to enable (1) including the product releases related to the issue, (2) adding releases in which the issue is resolved. The MicroComp management is particularly concerned with the security, accessibility, cost-effectiveness, and scalability of the IssueTracker system. MicroComp management has allocated a budget of $625 , 000 and a hard deadline of April of next year for project completion, so that it can be in place to ensure client satisfaction. They also expect the IssueTracker software to allow clients to report issues through a website that shall be usable on many browsers, with support for PC and mobile. The IssueTracker software should allow clients to sign up on the website by providing the related information. Clients are eligible to sign up if they previously bought a product, and they can provide a license key that can be validated by the client management system. Each license key can only be used by one client, and depending on the license, the clients are eligible to report issues related to a product. A client may add more than one license to be allowed to report issues for more than one product. All operations by clients are expected to be handled with minimum inputs from users. Thus, IssueTracker’s user interface should be efficient and easy to use. The IssueTracker software should enable many clients of the company to open issues, see a list of their own previously reported issues, and access the knowledge base and articles related to the licensed products. Each time a client chooses to view an article related to a product, the system must perform a quick check to ensure that the client is eligible to see the article. When opening an issue, a client should provide complete information. Providing the product name, affected releases, and description of the issue is mandatory, but the rest is optional. When a client views an issue, the system should allow the client to see the responses submitted by the technical experts, and request auto-notification when there is an update with the issue. The auto-notification should be sent by an email as soon as updates occur. When an issue is opened, its status is set to open, and then assigned when a technical expert is assigned to the case. The technical expert Page 2 of 4
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
  • Access to all documents
  • Unlimited textbook solutions
  • 24/7 expert homework help