Software Engineering

WAC: Business Requirements for AMMS Paperless Work Order Project

Submitted To
Dr. Zubair A. Sheikh, Miss Nida Mumtaz Name: Roll No: Date:
M.Saad Siddiqui k060110 2nd April 2010
1

Table of Contents
Project Summary................................................................3 Scenarios............................................................................4 Requirements Traceability Matrix......................................6 Methodology......................................................................7 System Dependability........................................................8 System Architecture...........................................................9 Conclusion........................................................................10 References.........................................................................11

Project Summary Facilities Maintenance department handles all requests through its Maintenance Dispatch Center (MDC), which uses scheduler utility to sort-out work orders for each crew and print them to Maintenance Managers. Crew members make notes/papers on work orders and return those papers to MDC for data entry into database. High volume of work orders causes high volume of paperwork, high paper costs, data entry delay, data entry errors, false reports, transportation costs, revenue losses and environmental pollution. Paperless Work Order Project is solution to all these problems, in which paperwork is eliminated to improve business processes of Airport Maintenance Management System.

Scenarios Trouble Calls Work Order Actors:Requester, AOCC, Scheduler, Crew, Maintenance Manager/Senior Mechanic, MDC Feature:Trouble calls work order schedule, assignment, update, review and submission Pre-condition: Requester contacts AOCC or MDC
Scenarios

Step 1 2 3 4

Action Requester contacts AOCC/MDC Scheduler schedules work order Crew updates work order

Maintenance Manager/Senior Mechanic reviews the work order 5 Data Entry by MDC Alternate Scenarios: None
Post Conditions

System Reaction Information recording in T.C Log Data transmission to AMMS Work order printed for Crew delivery Assign work order to crew Work order submission to Maintenance Manager/Senior Mechanic Work order delivery to MDC Save data into AMMS database

Step 1

Description Work order status can be checked in scheduler.

Projects Work Orders Actors: Technical Specialists, Scheduler, Crew, Maintenance Manager/Senior Mechanic, MDC Feature: Project work order schedule, assignment, update, review and submission Pre-condition: Technical Specialists sends the requests and schedules
Scenarios

Step 1 2

Action Technical Specialists sends requests and schedules Scheduler schedules work order

System Reaction Information recording in T.C Log Data transmission to AMMS Work order printed for Crew delivery Sorts work orders Assign work order to crew Work order submission to Maintenance Manager/Senior Mechanic Work order delivery to MDC 4

3 4

Crew updates work order Maintenance Manager/Senior Mechanic reviews the work order

5 Data Entry by MDC Alternate Scenarios: None

Post Conditions

Save data into AMMS database

Step 1

Description Work order status can be checked in scheduler.

Actors: Feature: Pre-condition:

Scenarios

Shift Close Work Orders MDC Decisions Crew, Maintenance Manager/Senior Mechanic, MDC MDC decides what to do when closing a shift None Software Reaction Work order submission to Maintenance Manager/Senior Mechanic Work order delivery to MDC

Step 1 2

Action Crew updates work order

Maintenance Manager/Senior Mechanic reviews and decides status of work order 3 Maintenance Manager indicates Work order status in AMMS is finalized that work order is 100% complete Alternate Scenarios: 1: Maintenance Manager indicates that work order is untouched, work order goes back in scheduler Holding Bay 2: Maintenance Manager indicates that work order has missing information or is incomplete, work order is sent to Maintenance Manager/Senior Mechanic 3: Maintenance Manager indicates that crew wants Technical specialists attention, email is sent to Technical specialists 4: Maintenance Manager indicates that maintenance managers/senior mechanics are required back in next shift, work order is assigned back to Maintenance Manager/Senior Mechanic 5: Maintenance Manager indicates that work order has incorrect data, and for correction it goes to MDC 6: Maintenance Manager indicates that work order has outstanding status(no Work performed), work order goes back to Holding Bay
Post Conditions

Step 1

Description MDC handles work order depending on status set by Maintenance Manager

Requirements Traceability Matrix Req. ID 2.1 2.2 2.3 2.4 2.5 2.6 2.7 2.8 2.9 2.10 D R R R D D R D R D R D R R D D D D D R D D D 2.1 2.2 D 2.3 D 2.4 D 2.5 2.6 2.7 2.8 D 2.9 R 2.10

Here, 'D' indicates that requirement in a row depends on requirement in a column. 'R' indicates a weaker relationship between requirements. For Example: User Requirements depend on Security Requirements, Data Requirements, Automatic Notifications, Legal Requirements and is in weak relation with Integration and Scalability Requirements.

Methodology

Since it is a huge project and there is much risk involved, waterfall model can not be used as security requirements and environmental requirements are ambiguous at some places. The requirements may change and thus waterfall will not be a good option. As there are a large number of crew members (250) , it does not seem feasible to apply Agile model. In short, Spiral model fits best here, and I will use Spiral model for this kind of system.

 Resource Requirements: Hand-held devices, firewall server, database servers, automation servers, about 300 kiosks/desktops, Internet connection and at-least 2 rooms for servers. System Dependability Availability: about 0.75 Reliability: about 0.75 for 4-5 years Safety: about 0.2 Security: about 0.1

System Architecture

Performance: To increase performance distributed database can be used. Security: For security besides user login system, a firewall can also be used. Safety: For safety reasons a number of servers should be used for real-time synchronization. Availability: Distributed database and more than 1 server will satisfy the availability issues. Maintainability: Database server should be separate and the server performing automation of notifications, printing and email should be different. Client-server model is applicable here, because automation needs to done with respect to email and printing, also AMMS Database should be accessible to hand-held devices and desktop computers.

Conclusion The system is analyzed, it is found that spiral model should be used for this type of project, it is quiet dependable and it's architectural design should be client-server.

10

References http://www.gtaa.com/en/home/ http://images.google.com http://blog.hydro4ge.com/wp-content/uploads/2007/12/h4_spiral.jpg http://www.ozdox.com.au/Graphics/Images/Worldox%20Total%20Paperless%20Office.gif

11