NAVSEA Liaison Scott Huseth Faculty Advisor Dr. Jiang Guo Team Members Areg Abcarians David Ballardo Niteen Borge Daniel Flores Constance Jiang June 3, 2010 Re-Engineering TFRMQS

Vision Statement TFRMQS Trouble/Failure Report Management Query System Vision of this project is Support contractors, uniformed personnel, SSP, and other government users Access information of TFRs. Improved usability of TFRMQS.

Software Purpose Convenient query management system. Retrieve TFRs on a user friendly web interface. Improve web front interface and backend database with today technologies.

Software Scope TFRMQS software is designed for: Customers, contractors, and NAVSEA personnel with basic skills to use the application. TFRs are generated and used by: Sailors while on patrol. Contractors to solve sailors report. TFRMQS allows users to search for TFRs and TFR/CARs.

Software Perspective Users will see TFRMQS as an easy way to search for TFR or TFR/CAR related information submitted by sailors and contractors. Users will have two methods of search : Query by form Query by wizard.

David Ballardo

Requirements Overview Time Spent on Requirements: 3 months (Fall Quarter) IEEE 830 Software Requirements Specification UML Standard Use Case Diagrams Software Requirements Review Meeting

Software Requirements Specification Currently a 121 page document Lists background information necessary to understand the rest of the SRS (Software Scope, Purpose). Operating Environment constraints Development constraints System Features (Functional Requirements) Use Cases

UML Diagrams – Use Case Description of a system’s behavior, describing who can do what with the system. Includes a list of interactions between system and user required in order to achieve a user goal.

Use Case Diagram Examples

Software Requirements Review Meeting to discuss SRS Opportunity to discuss the scope of the project, and to warehouse requirements. Required approval of a final SRS in order to move to design phase.

Daniel Flores

Design Intro Design Time: 1 quarter (Winter) Architecture: ASP.NET 3.5 MVC World Wide Web Consortium (W3C) IEEE Design Standard - IEEE Diagrams: Context Diagrams Sequence Diagrams Activity Diagrams

Architecture: MVC

MVC (Continued)

World Wide Web Consortium (W3C) “[W3C] is the main international standards organization for the World Wide Web...” - Wikipedia.com W3C was the standard used when designing the GUI for our project. Even though our design was structured using this standard for the most commonly used browsers, the GUI design was made for IE7 and above.

IEEE Design Standard IEEE Software Design Description. IEEE standard that specifies an organizational structure for a software design description (SDD). An SDD is a document used to specify system architecture and application design in a software related project.

IEEE Software Design Description (SSD) 1. INTRODUCTION 1. Design Overview 2. Requirements Traceability Matrix 2. SYSTEM ARCHITECTURAL DESIGN 1. System Architecture 2. System Interface Description 3. DETAIL DESCRIPTION OF COMPONENTS 1. List of Components 4. USER INTERFACE DESIGN 1. Description of the User Interface 1. Screen Image 2. Objects and Actions 5. ADDITIONAL MATERIAL

Project Layers Business Layer Contains all the classes/functions that are used by the controllers to manage requests for the Data Later. Data Layer Contains all the classes/functions that are used to retrieve data from the database and return it to the Business Layer. UI Layer Contains all the.aspx and.ascx pages that render the data from the models (Data Layer) which is what the user sees. Also, contains the (Controllers) which handle events from the user (client).

Diagrams – Context Diagram

Diagrams - Sequence Diagram

Diagrams - Activity

REQUIREMENTS TRACEABILITY MATRIX

Areg Abcarians

Development Coding Time Span: 4 Months First Month: Environment Setup Visual Studio 2008 Oracle 10g XE AnkhSVN (version control plugin)

Coding and.NET Code Written in: HTML / CSS / JavaScript Initial layout of application design (pretty straight-forward).NET (C#) There was a learning curve Started to study.NET and experimenting with the C# language Upon familiarity, started to study NAVSEA coding standards given to us Purpose was to ensure consistency in code

Database Second Month: Database Connection Code Oracle 10g installation went smoothly 32-bit vs. 64-bit operating systems issue After setup, NAVSEA provided us with artificial sample data to populate database with The coding process had begun

Code Reviews Third Month: First Code Review with NAVSEA Required changes and fixes were made Advised about how to make code more efficient

The Final Stages The deadline was approaching Lots of coding done to finish things up Second Code Review at NAVSEA (tested application on their system and integrated with their large database) Not every feature had been implemented yet and application was still buggy Final code review at NAVSEA uncovered some final product bugs had sufficient time over there to resolve those quick fixes

Constance Jiang

Software Testing Testing documentation written in IEEE standard format Testing took place both during development and after Documents consisted of test plan, cases, and procedures

Test Plan Overall summary of testing Hardware Requirements Items to be tested Pass/Fail Criteria Problem Reporting

Test Cases Created based on Use Cases in SRS Outlines correct input and output References other test cases that need to be performed prior Includes a matrix to check off pass/fail for each step

Test Procedures A test procedure for each test case Expands on inputs/outputs listed in Test Cases Lists step-by-step actions to be taken and the correct output