Revised System OverView - Amel94/ITC309 GitHub Wiki

REVISED SYSTEM OVERVIEW

Revised ER Diagram

ER Diagram Breakdowns

  1. Employee Has Allocation

2.Employee Add User

Allocation Has Projects

1.3 Revised Full ER diagram

REVISED DESCRIPTIVE USECASE

Title Descriptive title for the use case of the project “resource allocation system.” Actors Primary Actors (Secondary Actors) Normal Flow User and the employee login to the system. User can add employees Employees can add allocation. /Update Allocation Employees can check reports.

An Alternate Flows If the project proceedings are not successful, then the employees can cancel the project

Sub flows Obtain project information from the employees Pre- conditions Post-conditions Employees can check the progress of the project

Use Case Diagram Description This use case describes the process involved in allocating resources to a project. It covers operations like creating a project, selecting and allocating resources to a project, updating project status and cancelling a project. The Employee and the user perform all these operations. It also covers operations like viewing projects assigned to a resource, tasks covered under a project, entering actual and estimated time to complete a project. Also, business sponsors can view the status of the sponsored projects.

Actors Employees, User Pre-Conditions The Employee should initiate project, add allocation and check reports. Check reports consists of Employee wise, project wise and Booking wise. User Have access to login and add employees to the system.

Normal Flow

  1. User Have Access to login the system.
  2. After login to the system user can Add employees. Also, it can be update.
  3. Employees create project. There are two options as add and update.
  4. The project can also be cancelled by the Employee.
  5. Project Employees can login to the system and view the status of the project.
  6. Project Employees can update the project status based on project planning, implementation.
  7. Employees can view the projects assigned to them, tasks under the projects.
  8. Once tasks are assigned the resources can enter the estimated time for the task
  9. Once task is completed by employees, they can check the errors and progress of the work done.
  10. Employees add allocation.
  11. Allocation can be updated by the employees.
  12. Employees can check reports.
  13. Check reports can be done by employee wise, project wise and booking wise.

Actor System Pr User Ma Add Employees .

Actor System Project manager Create the project

Alternate Flows If the project proceedings are not successful, then the employeecancelthe project

Sub flows Obtain status of the project

Key Scenarios Key scenarios can be defined as any scenario that meets one of the following requirements Architecturally significant use case. Intersection of quality attributes with functionality. In this scenario key scenario is quality of the project.

Post-conditions Employee check the progress and errors of each tasks.

Special Requirements Special requirements include these factors such as  Legal and regulatory requirements  Quality attributes of a system Ex: - usability, reliability, performance, and supportability  operating systems and environments operating systems and environments

REVISED USECASE DIAGRAM BREAKDOWNS

User Login to the system

User add Employees

Employees Create Project

Employees add allocation to the project.

Employee check Reports, Employee wise, booking wise, Project wise.

Revised Full Use Case Diagram Functional Requirements

  1. FR01: Provide a web interface that allows user to view project and employees  FR01.1: Resource Utilize overview  FR01.2: Project overview  FR01.3: personnel Overview

2.FR02: Provide a web interface to allow Employees to modify personnel and project information  FR02.1: Add new personnel to the project  FR02.2: Edit project attributes  FR02.3: Update project progress

3.FR03: Provide printable reports  FR03.1: Resource Availability reports.  FR03.2: Client programmed / project report

FR04: Interface with database to retrieve personnel information Non-Functional Requirements

• NFR01: RAS Must be able to be accessed from any location with internet access. • NFR02: RAS must be able to scale as zirous grown in size. • NFR03: RAS must be an easier to use than the current spreadsheet solution • NRF04: RAS must be able to handle multiple concurrent users’ employees using the system. • NFR05: The web interface must be responsive to user input. • NFR06: RAS must be developed in a manner that makes it easy to maintain and improve the future.

CCRD use case Definition

A “Use Case describes the interaction (triggered by an external actor in order to achieve a goal) between a system and its environment. A Use Case defines a goal-oriented set of interactions between external actors and the system under consideration. The term actor is used to describe the person or system that has a goal against the system under discussion. A primary actor triggers the 12-system behaviour in order to achieve a certain goal. A secondary actor interacts with the system but does not trigger the Use Case” CCRD Use case includes following characteristics.

C-Critical C-Core R-Risky D- Difficult

Critical in the Use case Visualize the Critical things in the software development project. Ex: - Project manager controls the projects and the employees. Core Functionalities of a system and Visualize the interaction of various things called as actors of the use case.

CCRD USECASE Title CCRD use case for the use case of the project “resource allocation system.” Primary Actors (Secondary Actors) Critical and Core Project manager and employee’s login to the system. After creation of a project resources employees are selected for the project and assigned to it. Project manager Assign tasks of the project for the employees The project can also be cancelled by the manager. Project Manager can login to the system and view the status of the projects sponsored by them Project managers can update the project status based on project planning, implementation. Employees can view the projects assigned to them, tasks under the projects. Once tasks are assigned the resources can enter the estimated time for the task Once task is completed project manager can check the errors and progress of the work done by employees. HR department manage the employees. Employees Payroll is done by HR Department. Employees Payroll is depending on the attendance of the employees. Risk If the project proceedings are not successful, then the project manager can cancel the project

Obtain project information from the employees

Difficult Project manager can check the progress of the project