SystemWideRequirements

• System-Wide Requirements Specification
  • Introduction
  • System-Wide Functional Requirements
  • System Qualities
    • Usability
    • Reliability
    • Performance
    • Supportability
  • System Interfaces
    • User Interfaces
  • System Constraints

System-Wide Requirements Specification

Introduction

The purpose of this document is to describe the system-wide requirements in sufficient detail to validate understanding of the requirements, to ensure concurrence with stakeholder expectations, and to permit software development to begin.

System-Wide Functional Requirements

Authentication: The product shall use Windows Authentication or Forms Authentication. The Software Development Team must evaluate the best option.

Licensing: The Software Development Team must evaluate the best Open Source License that allows the use of .NET Framework.

Printing: The product shall print document using a user-friendly, simple and international standardize format.

Reporting: The product shall print documents using HTML format.

Security: The product shall control all the access to the information.

Exporting: The product shall be able to export to XML files all the data stored in the database.

System Qualities

Usability

Task efficiency: The product shall allow the addition and modification of TL entries through a single mouse click or a keyboard hit whenever possible.

Ease of remembering: The product shall be easy of remembering. This can be accomplishing by the fact the product will have a similar look and feel to Gmail mail service.

Understandability: The product shall follow the Microsoft Inductive User Interface Guidelines.

Reliability

Accuracy: The product shall store and display the time data in minutes.

Availability: The product shall be available the working time of the Engineer. The Mean Time Between Failures (MTBF) shall be 15 days.

Recoverability: The product shall recover from failure in less than 1 day (Mean Time to Repair).

Performance

Response times: Any interface between a user and the system shall have an average response time of at most 2 seconds. The reports are an exception to this rule (they can take 20 seconds or less).

Supportability

Adaptability: The product shall be designed in a way that multiples user-interfaces can make use of it. Examples are: Web Application, Windows Forms, Windows Presentation Foundation (WPF), etc.

System Interfaces

User Interfaces

Look & Feel: The product shall have the same look & feel as Gmail email service.

Layout and Navigation Requirements: The product shall have categories of the time log entries to the left side and the main menu at the top of the window. A grid containing the time log entries shall be located at the center. All this is similar to behavior of dynamic elements of Gmail mail service.

Consistency: When creating or editing an item (e.g. category, time log entry, etc) the position of the controls shall be consistent: It shall have a Window Title, followed by the labels and their corresponding edit boxes. At the bottom of the window, the required buttons shall be in place being 'Cancel' button the last one from left to right. See the figure below:

System Constraints

Design constraints: The product shall be developed as a Web application.

Implementation languages: The available programming language is C# and the web application framework is ASP.NET. The Software Development Team must define the best DBMS for this project.

Physical Constraints: The available Web Server has installed Windows 7 operating system.

---

Copyright Š 2009, 2011 Paulo Sequeira, Lenin Sibaja

The PSPLogger project documentation is licensed under a Creative Commons Attribution 3.0 Unported License.