Shared by 
Unlock all 16 pages
Get it free by sharing your own notes, buy just this one, or become a member and unlock documents with your plan.
How to unlock this document
Choose the way that suits you. Each one gives you all 16 pages to read online and the PDF to download.
Share your notes, unlock for free
2 free unlocks for every 5 approved uploads
- Upload your own lecture notes, assignments, essays or past papers
- PDF, Word, PowerPoint and Excel files all work, and you can send many at once
- We check each upload; you get a notification when it is approved
- Spend a free unlock on this document or any other, and keep it for good
- Shared under your public username, never your email
Then upload your notes from your profile.
Buy this document
$16 one-time payment
- All 16 pages of this document, yours to keep
- Download the PDF and read it any time, also offline
- No subscription and nothing to cancel
- Find it again any time under My Profile → Library
You log in or create a free account first, then pay securely.
Become a member
Unlock documents from the whole library, which keeps growing
- Choose any documents you like, up to your plan’s unlocks
- Documents you unlock stay yours, even if you cancel later
- Your unlocks start again with every renewal
- Secure checkout by Dodo Payments
You log in or create a free account first, then pay securely.
Compare the plansAlready a member, or bought this before? Log in to open it
About this document
- Pages
- 16 pages
- Price
- $16 one-time, yours to keep
- Membership
- Included in every plan
- Format
- Subject
- Computer Science, Software Engineering
This document outlines the software requirements for a Problem Tracking Tool. It covers the system’s functional requirements, user interface specifications, external interface specifications, and other requirements. It is useful for students studying software requirements specifications.
What's inside
- Introduction to the Problem Tracking Tool
- Functional Requirements
- User Interface Specifications
- External Interface Specifications
- Other Requirements
Who it is for: Students of Software Engineering, Computer Science, or Information Technology courses studying software requirements specifications. (Undergraduate)
Share with classmates: WhatsApp Telegram X LinkedIn Facebook
Summary
A problem tracking tool is a software system for managing and resolving issues. Students learn about the tool's features, user roles, and technical requirements.
System Scope and Entities
The problem tracking tool is a standalone system. It describes the roles of customers, support staff, managers, administrators, and developers. It also lists the entities involved in tracking problems.
User Roles and Permissions
Different users have specific permissions. Developers can manage their own solutions and change requests. Managers can update problem statuses and assign tasks. Administrators have full control over cases, solutions, and change requests.
Functional Requirements
The tool supports creating, modifying, searching, and deleting cases, solutions, and change requests. It also includes modules for modifying and searching information. It does not generate reports or support wildcard functionality.
Technical Requirements and Adaptation
The system runs on specific hardware and software. It requires C and TAL programming, and an SQL database. The system is adaptable to different sites and users.
Key terms
- Case
- A problem reported by a customer to support staff.
- Change Request
- A request for a fix, including design, code, and test information.
- Solution
- The analysis of a case by a developer or support staff.
- Navigation Chart
- A chart showing the access routes to the screens.
- User Access Control
- Security measures to control who can access the system and what they can do.
- Performance Requirements
- The system's availability and performance needs, like response times.
Questions this document helps with
- Who can create and delete solutions in the problem tracking tool?
- What programming languages does the tool require?
- How does the tool control user access and security?
Summary written with AI from the document's text.
Ask the AI Teacher
Ask any question about this document or your course, and get a clear explanation.
Log in to ask Create a free account
Free accounts can ask 5 questions a day.