Part A - Requirements
R1 The software should allow companies to be created R1.1 The software should allow projects to be created R1.2 The software should allow users to be created R1.3 The software should allow tickets to be created
R2 The software allows the users to read and update the following:
R2.1 Companies R2.2 Projects R2.3 Other Users
R2.4 Tickets and state of tickets
R3 Projects must be able to be assigned to companies R3.1 Users must be able to be assigned to projects R3.2 Tickets must be able to be assigned to users
R3.3 The state of the tickets can be changed by the user
R4 The software allows the user to delete companies R4.1 The software allows the user to delete projects R4.2 The software allows the user to delete other users R4.3 The software allows the user to delete tickets
R5 Software can produce reports
R5.1 The software should display the productivity of users within the report
R5.2 The software should show the progress of development within the report
R6 Users can build a board that displays tickets
R7 The software will allow a user to predict the number of projects that a company will work on and the appropriate number of people needed to build these projects based on previous data
R7.1 The user can produce a prediction for a specific date NON FUNCTIONAL REQUIREMENTS
NF1 Application will run on Windows and not any other operating system
NF2 Application should be a programmatic dynamic interface
NF3 Application data will be saved in a persistent form such as inside a database
NF4 Application can read and write the data and activity is threaded
NF5 Application is built as a .NET C# application
Part B - Use case Diagrams
Part B - Use case Diagrams II
PART B - USE CASES
Use Case: Register
Id: UC-‐ 001
Description: Users can register a set of login details unique to them
Primary Actor: User
Supporting Actors: Database
Stakeholders and Interests: No stakeholders and interest
Pre-‐Conditions: Not an existing user
Post Conditions: Upon successful registration, the user can use these details to log into the system
Trigger: The user presses the register button
Main Success Scenario
1. The user presses the register button
2. Users enter information to register.
3. The system validates the input data from the user.
4. User details are now stored in the database system.
5. Users can log in using details they used to register
Variations: No variations
Use Case: Login
Id: UC-‐ 002
Description: Users use the details they registered with and enter them into the login screen
Primary Actor: User
Supporting Actors: Database
Stakeholders and Interests: No stakeholders and interest
Pre-‐Conditions: Not an existing user
Post Conditions: Upon successful registration, the user can use these details to log into the system
Trigger: The user presses the register button
Main Success Scenario
1. The user enters their login information
2. The system checks and authenticates user details
3. Access is granted
DescriptionIn this final assignment, the students will demonstrate their ability to apply two ma
Path finding involves finding a path from A to B. Typically we want the path to have certain properties,such as being the shortest or to avoid going t
Develop a program to emulate a purchase transaction at a retail store. Thisprogram will have two classes, a LineItem class and a Transaction class. Th
1 Project 1 Introduction - the SeaPort Project series For this set of projects for the course, we wish to simulate some of the aspects of a number of
1 Project 2 Introduction - the SeaPort Project series For this set of projects for the course, we wish to simulate some of the aspects of a number of