Determine the skill level of human resources (in either novice (entry level), intermediate (junior) or advance(senior).) for each particular project in order to estimate human resources costs. ( R.1 Feature Style)

Calculate the total time that require for each project within 10% deviation. (R1, Feature Style)

Calculate time use for each phase during the development process base on historical data. (R2, Feature Style)

Integrate Microsoft Project software with the ability to show the total number hours that each project required and booked as a Gantt chart on Microsoft Project. (R3, Standard Style)

Record current data and retrieve historical data for client projects. (R1, Usability Style)

Allow novice users retrieve historical data and to record new client information in 10 minutes. (R10, Usability Style)

Compare profitability of different projects in order to allow management identifies the profitable one. (R1, Feature Style)

Break down individual task needed to complete project and grade its complexity in easy, medium, or difficult. (R1, Feature Style)

Allow manager complete estimation process by doing the following tasks:

Prevent unauthorized access to system data 99.9% of the time. (R6, Usability Style)

1. Introduction

1.1 Purpose

The purpose of the system is to help a project manager to accurately estimate software projects and meet clients’ required delivery date.

1.2 Intended Audience and Reading Suggestions

The readers are the developers, project manager, marketing staff, users, and testers.

1.3 Document Conventions

When writing this SRS we use functional and nonfunctional requirement styles. Every requirement statement in this SRS has its own priority.

1.4 Product Scope

Refer to Rationales.

1.5 References

2. Overall Description

2.1 Product Perspective

2.2 Product Functions

The system shall be a system that is specifically design for a particular company.

2.3 User Classes and Characteristics

The system shall be use by employee of the company especially project manager.

2.4 Operating Environment

The system shall be used in an office environment where employee will input information into the system. Refer to Requirement #4 and Use case #3.

2.5 Design and Implementation Constraints

The system shall have an ID and password security code for employee of the company so that not all employees are able to assess the system.

2.6 Assumptions and Dependencies

The designer of the system assumes that the requirements of the clients have not change. The designer of the system assumes only the employee of the company are using the system. The designer of the system depended on the assumption that no major changes in technology will change cause the system to be second-class technology.

3. External Interface Requirements

3.1 User Interfaces

Refer to Requirement #4 and Use case #3.

3.2 Hardware Interfaces

None

3.3 Software Interfaces

Refer to Requirement #4 and Use case #3.

3.4 Communications Interfaces

None.

4. System Features

Refer to each Requirement and Use Case for detailed description, stimulus/response sequences, and functional requirements associated with each feature.

4.1 Estimate Revenue for Projects

Refer to Requirement 9, Use Case # 7.

4.2 Estimate Complexity of Projects

Refer to Requirement 8 and 9, Use Case # 2.

4.3 Calculate Estimated Costs and Time Required for Completion

Refer to Requirement 2, 3 and 9, Use Case # 4.

4.4 Estimate Available Human Resources

Refer to Requirement 1, Use Case #1 and #6.

5. Other Nonfunctional Requirements

5.1 Performance Requirements

Refer to Requirements 2, 6, and 10 and Use Cases 4, 5, and 9.

5.2 Safety Requirements

None.

5.3 Security Requirements

Refer to Requirement 10.

5.4 Software Quality Attributes

Refer to Requirement 9 and Use Case 7.

5.5 Business Rules

Refer to Requirement 1 and Use Cases 1 and 6.

5.6 User Documentation

User manual, online help, and tutorial will be included with the software.