Residential Safety Office Business Case

Business Case
RESIDENTIAL SAFETY OFFICE (GOGREEN INITIATIVE) AT NORTHEASTERN UNIVERSITY

VERSION 1.0 DATE 04/21/2013
Residential Safety Office (GoGreen Initiative) Table of Contents

1. EXECUTIVE SUMMARY .................................................................................................................... 4 1.1. Issue .................................................................................................................................. 4 1.2. Anticipated Outcomes ...................................................................................................... 4 1.3. Recommendation ............................................................................................................. 5 1.4. Justification ....................................................................................................................... 5 2. BUSINESS C ASE ANALYSIS TEAM ....................................................................................................... 6 3. PROBLEM DEFINITION .................................................................................................................... 7 3.1. Problem Statement........................................................................................................... 7 3.2. Organizational Impact....................................................................................................... 8 3.3. Technology Migration ..................................................................................................... 10 3.4. Project Overview: ........................................................................................................... 10 3.5. Project description:......................................................................................................... 11 3.6. Goals and Objectives ...................................................................................................... 11 3.7. Project Assumptions: ...................................................................................................... 12 3.8. Project Constraint ........................................................................................................... 12 3.9. Major Project Milestones ............................................................................................... 12 4. STRATEGIC ALIGNMENT ................................................................................................................ 19 5. C OST BENEFIT ANALYSIS ............................................................................................................... 20 6. ALTERNATIVES ANALYSIS ............................................................................................................... 24 7. REQUIREMENTS DOCUMENT.......................................................................................................... 25 7.1. EXECUTIVE SUMMARY .............................................................................................................. 25 7.2. ASSUMPTIONS, RESTRICTIONS & LIMITATIONS............................................................................... 26 7.3. DATA FLOW ............................................................................................................................ 26 7.4. CUSTOMER WORKFLOWS.......................................................................................................... 27 7.4.1. AS-IS BUSINESS USE CASES AND ACTORS.................................................................................. 27 7.4.2. TO-BE USE-CASES AND ACTORS ............................................................................................. 28 7.5. BUSINESS AND FUNCTIONAL REQUIREMENTS................................................................................. 30 7.5.1. PAPERLESS SOLUTION ........................................................................................................... 30 7.5.2. EFFICIENT SHIFT AND BREAK MANAGEMENT ............................................................................. 30 7.5.3. SHIFT ALLOCATION ............................................................................................................... 30 7.5.4. HR MANAGEMENT .............................................................................................................. 31 7.6. GENERAL REQUIREMENTS.......................................................................................................... 31 7.6.1. DATA STORAGE ................................................................................................................... 32 7.6.2. DATA DE-IDENTIFICATION...................................................................................................... 32 7.6.3. DATA VALIDATION ............................................................................................................... 33 7.6.4. DATA AND USER ACCESS ....................................................................................................... 34 7.7. AUDITING............................................................................................................................... 34 7.8. USABILITY............................................................................................................................... 34 7.9. RELIABILITY............................................................................................................................. 35 7.9.1. PERFORMANCE .................................................................................................................... 36 7.9.2. SUPPORTABILITY .................................................................................................................. 36 7.9.3. SYSTEM AVAILABILITY ........................................................................................................... 36
Business Case v 1.0 Page 2
Residential Safety Office (GoGreen Initiative)

7.10. INTERFACES......................................................................................................................... 37 7.10.1. USER INTERFACES ............................................................................................................. 37 7.10.2. HARDWARE INTERFACES .................................................................................................... 37 7.10.3. SOFTWARE INTERFACES ..................................................................................................... 37 7.10.4. COMMUNICATION INTERFACES............................................................................................ 38 7.10.5. DATA MIGRATION INTERFACES............................................................................................ 38 7.10.6. PURCHASED C OMPONENTS................................................................................................. 38 7.10.7. LICENSING REQUIREMENTS................................................................................................. 38 7.10.8. LEGAL, C OPYRIGHT AND OTHER NOTICES .............................................................................. 39 7.10.9. DOCUMENTATION REQUIREMENTS ...................................................................................... 40 7.10.10. USER ACCEPTANCE TEST STRATEGY ...................................................................................... 41 7.11. USE C ASES.......................................................................................................................... 42 8. HIGH LEVEL SYSTEM OVERVIEW : .................................................................................................... 50 9. DIAGRAMS AND PROCESS FLOWS: ................................................................................................... 51 10. USER INTERFACE SCREENSHOTS .................................................................................................. 58 11. REPORTS................................................................................................................................ 61 12. APPENDICES.............................................................................................................................. 1 13. REFERENCED DOCUMENTS........................................................................................................... 2 14. APPROVALS .............................................................................................................................. 2
Business Case v 1.0
Page 3
Residential Safety Office (GoGreen Initiative) 1. EXECUTIVE SUMMARY

This case study examines and shows the implementation strategy of Residential Safety Office and how the GoGreen initiative is used to eliminate the entire paper based system and efficiently performs the daily critical and routine tasks. This migration of the system will be a bigbang approach where all the system are shifted to new implementation while keeping the cost within the budget and achieve short term as well as long term profit through this paperless system. Using this new system at RSO operations will be easier and safety operations will be more effectively managed by keeping focus on details.
1.1. Issue The Residential Safety Office of Northeastern University currently follows process that has paper based records. All the data is currently stored on papers and the information is not available online. The proctors cannot look up for shifts online and everything has to be done manually. The RSO office recruits new proctors every semester but that needs to be managed online. Currently a new proctor need to fill a paper based form and submit it. There is no record of a proctor online and he cannot view the status of the application online. So for every process that has a paper involved in it needs to be paperless. 1.2. Anticipated Outcomes Considering the fact that almost all the processes will be done online, the new proposed system will facilitate the work for Northeastern University RSO. The supervisors will be able to view the data immediately about a proctor. The proctor need not perform manual selection of the available shifts, everything will be available online. The RSO process will change into a paperless system and this will be eco-friendly process. The memos are currently told verbally to all the proctors, this will be visible to all the users in the newly proposed system. The recruitment process will benefit from this process as the student will be able to view the status of application and the result online. This will reduce any paperwork and make every process online.
Business Case v 1.0
Page 4

1.3. Recommendation The approach for this recommendation should be, all the supervisors and the proctors should be trained for the new system. For 6 months, both the systems will be active so as to make the users and the supervisors familiar with the new proposed system. This will be implemented in three phases; the duration of the first phase will be two months. The users will get introduced in first phase. In the second phase, it will be compulsory for the user, to use the new system. In the third phase the bugs and the fixes will be made based on the feedback from the users.
1.4. Justification Since starting this system, the approach has been without using any online-based system; even the swap board used in this system is from a third party. This is only used for swapping the users. The new approach will make everything online this will help in better traceability of a user, his information like who is doing what when where. This approach is also aligned with best strategy and objectives since it uses newer technology to improve the way we do business by replacing the older system. While other alternatives and the status quo were analyzed, this Project was selected for proposal in this business case because it provides the best opportunity to realize benefits for the greatest improvement in efficiency and cost reduction.
70% cost saving in project estimated budget. 60% immediate increase in proctor work efficiency in daily manner. 80% immediate decrease in the amount of time taken to sign in a guest. 98% reduction in maintenance due to paper elimination (GoGreen initiative). Effective increase in NUPD communication.
Business Case v 1.0
Page 5
Residential Safety Office (GoGreen Initiative) 2. BUSINESS CASE ANALYSIS TEAM

The following individuals comprise the business case analysis team. They are responsible for the analysis and creation of the Project business case.
Role Project Manager Business Analyst System Analyst Data Analyst Quality Engineer
Description Project managers can have the responsibility of the planning, execution and closing of any project. Identify and articulate the need for change in how organizations work, and facilitate that change. Identify, understand and plan for organizational and human impacts of planned systems. Specializes in collecting, organizing, and analyzing data from various resources. Monitors the software engineering processes and methods used to ensure quality. Creates the graphics primarily for published, printed or electronic media, such as brochures and advertising.
Name/Title Kaustubh Pathak Nisha Pepsi Selvarajan Pratik Zingade
Nilesh padwal
Pragati Dhavaleshwar
Graphic designer
Fenil Gandhi
Business Case v 1.0
Page 6
Residential Safety Office (GoGreen Initiative) 3. PROBLEM DEFINITION

3.1. Problem Statement Northeastern university has on campus Residential Security Office (RSO) whose primary responsibility is access control of the more than 40 residence halls. RSO manages its employees by a third party web based software to assign the employees shifts which has its own disadvantages including security, shift blocking, and improper scheduling process. The manual process of data filling and submission tasks is involved in proctor hiring process. The major challenges faced by the RSO are proctor management, workstation management, shift management, Cost and Staffing Management, Human Resource management and Incident Management. Poor organization of shifts among available proctors, Shift blocking in Swap board, No proper break management are not well managed by the existing third party software. Proctors get manual write-ups based on different rule violations which may include superfluous conditions. This increases restriction on proctors and encourages high attrition rate at RSO.As a result, to keep up with the workload RSO staff management keeps the resource pool large. This results in poor management, dissatisfaction of proctors and supervisors, insecurity of jobs and weak work ethics.
Goals and Objectives: To develop software which clock-in at the arrival and 'clock-out when proctors leave or
when they take the lunch break. This will lead to effective distribution of breaks and effective resource management. Retrieve guest details and Black list entries that are not welcome back while trying to make
an attempt to residence halls from the database. To propose a solution for better handling of emergency situations and disciplinary actions. To develop software which can eliminate draw backs of existing third party software like
shift conflicts and swap board blocking. To redefine existing manual process of proctor hiring process and writing works by proctors
during residence hall monitoring. Digital Memos are available in dashboard for every proctor as per their respective station.
Page 7
Business Case v 1.0

3.2. Organizational Impact 1. Impact on Manager a. Hiring Process: Instead of paper-based application process, manager can go through all the application easily through an application portal. The application portal can help manager sort appropriate candidate as per the requirement. Also, it would help RSO to follow its rules regarding applicants. For example, we can avoid first semester student applying by putting constraint in the web-application itself. IMPACT: Transparency in Hiring Process b. Staff Management: After every semester, a number of students graduation leads to a necessity of new proctors.
But, most of the times students fail to disclose their graduation which leads to an incorrect number of active proctor accounts (Which are used as buffer). The portal will link Northeastern University Students portal with RSO portal in order to identify and close the accounts of graduating student. By getting who will be able to work next semester, RSO can get to know about how many
proctors it should hire for the upcoming semester. This will allow RSO to distribute the shifts properly and assign each proctor proper amount of shifts. Managers can also get to know about a proctors performance easily. Through the web
portal, manager can get to know about a proctors write -up history and his performance. IMPACT: Proper Staff Management
2. Impact on Supervisor: a. Incident Management: Currently, supervisor manage all the incidents in an excel sheet which is very inconvenient.
The new portal will allow all the proctors sitting at the station to report incident directly. It will not only reduce work of supervisor but also increase reliability and efficiency By converting paper-based write up system to an online portal, assigning write-ups will be
easy and supervisor will be able to record it accurately.
Business Case v 1.0
Page 8

The new system will allow each proctor to directly start/stop the break. The relief proctor
will no longer need to call RSO in order to register the break timings. Also, it would make it more efficient and reliable compared to current excel sheet system.
2. Proctor: a. Workstation assignment: Currently, each proctor has to go one hour early in order to get assigned to a workstation.
Using the new system, proctors will be assigned their respective stations automatically, online only which will save an hour. The proctor will be able to go to their workstation directly w/o going to RSO station. They
can get signed in directly by swiping the card at the particular station IMPACT: time and effort saving.
Hardware/Software: In addition to the workforce impact, the online software need to be installed on the local server and domain name also be needed to publish the website. Server related hardware cost is included in the software deployment to keep the website up and running all times for staff.
Business Case v 1.0
Page 9

3.3. Technology Migration Technology migration occurs when changes require the organization switch to a different technology. Beyond the risks in technology migration, four key must be considered when attempting any IT system migration. The following is a high level overview of each phase: Phase 1: Readiness of the existing IT infrastructure, which consists of the servers, storage networks, and security technologies. New IT infrastructure must be purchased and make sure that every computer works well. Phase 2: Look at primary databases and determine if they are sufficient or need to be upgraded or migrated too. Phase 3: Check any custom applications running. They may have to be revamped or replaced or otherwise modernized Phase 4: Check with RSO packaged software providers to make sure their applications will run with new system. IBM has its Migration Factory which has some combination of tools, testing and assessment methodologies, and professional services to help migrate to technologies.
3.4. Project Overview: The RSO management project will provide detail for how this project will address the current Northeastern residential security business problem. The overview consists of project description, goals and objective, project performance criteria and major milestones. To ensure that only authorized residents and their guests enter University residences, Northeastern University provides uniformed security coverage twenty-four hours a day, seven days a week at the main entrances of the large residences. All students who enter the large residences must show their NEU ID Cards to the proctors each time they enter. When someone visits a resident of a large residence, they must be checked against the banned list and entered into guest details. All guests must leave a photo identification card at the security desk. No more than three guests per student are permitted at any time.
Business Case v 1.0
Page 10

Proctors can fill time availability and can pick their shift. Up-to-date staff availability information, no conflicts due to overlapping shifts, no scheduling conflicts will help to increase proctors satisfaction. Unfortunately RSO has lot of scope for improvement such as automating the process and to increase proctors satisfaction.
3.5. Project description: The mandate of the Residential Security Office, Northeastern University, is to improve workstation management. The manual process of data filling and submission tasks has to be automated. New solution has to be defined for effectively handling shift distribution to proctors and supervisors. Efficient Algorithm has been defined to prevent shift conflicts and swap board blocking. Better handling of emergency situations and disciplinary actions by connecting application with NUPD. Proctors will be able to add their breaks during each shift. Memos, Banned list and sign in sheets can be viewed online which will eliminate poor management, dissatisfaction of proctors and supervisors. The products the project will produce are: a DVD, an information kit for new users and software package. The tools that the organization will use to measure the results of the project are: surveys, pilot tests and focus groups involving proctors, supervisors, Residential Assistant and managers. management, shift management, proctor management and incident
3.6. Goals and Objectives To develop software which clock-in at the arrival and 'clock-out when proctors leave or when they take the lunch break. This will lead to effective distribution of breaks and effective resource management. Retrieve guest details and Black list entries that are not welcome back while trying to make an attempt to residence halls from the database. To propose a solution for better handling of emergency situations and disciplinary actions.
Page 11
Business Case v 1.0

To develop software which can eliminate draw backs of existing third party software like shift conflicts and swap board blocking. To redefine existing manual process of proctor hiring process and writing works by proctors during residence hall monitoring. Digital Memos are available in dashboard for every proctor as per their respective station.
3.7. Project Assumptions: The following assumptions apply to residential security management. Funding is available for training. Funding is available for purchasing hardware/software for residential security management. Project has executive level support and backing All department head will provide necessary support for successful project completion. All staffs and employees will be trained according to their respective data entry, Timesheet and reporting tasks.
3.8. Project Constraint The development or operating environment is new, and no project staff members are familiar with it. Deliverables submitted for approval will require working days for review. Cannot produce high quality on a restricted budget and within a tightly restricted time schedule. The estimated staff resources needed to complete the project, according to number, type, work hours, and skills can be inaccurate.
3.9. Major Project Milestones The following are the major project milestones identified at this time. As the project planning moves forward and the schedule is developed, the milestones and their target completion dates will be modified, adjusted, and finalized as necessary to establish the baseline schedule.
Milestones/Deliverables Project Charter Project Plan Review and Completion Project Kickoff Phase I Complete Phase II Complete Phase III Complete Closeout/Project Completion
Target Date 01/21/2013 02/11/2013 02/18/2013 03/07/2013 03/24/2013 04/14/2013 04/20/2013
Business Case v 1.0
Page 13
Release Planning
Sprint 1 Feb12-Feb 25
Register as proctor, supervisor. Login as Proctor/Supervisor.
Sprint 2 Feb 26-Mar 11
Submit and view memos, banned list, online sheets.
Sprint -3\ Release 1 Mar 12-Mar 25
Swap board, Picking the shift, Setting the availability, view schedules.
Sprint 4 Mar 26-Apr 8
Proctor online training material, Download application form .View results of exam.
Business Case v 1.0
Page 14

Release 1 Burn Down chart
Business Case v 1.0
Page 15

Release 2 Burn Down chart
Business Case v 1.0
Page 16

Cumulative Flow for Release 1 &Release 2
Business Case v 1.0
Page 17
Total effort for the project
Business Case v 1.0
Page 18

4. STRATEGIC ALIGNMENT The Residential Safety Offices primary responsibility is access control of the residence halls. Access control is achieved with a comprehensive package of "people protecting people," while utilizing a computerized electronic access control system and various alarms.
We aimed the following key factors which can be achieved using respective module of the system.
1. Security : RSO being the primary center for security of all the residential halls, the system aims to improve this by providing a better solution which guides proctors and by intuitively indicating accesibility and thus reducing scope of any human error. The system also provides an interface to quickly access all the information about anyone entering the residence hall at a particular time.
2. Efficient Staff: In any organization, the efficiency is measured by its staff. Through performance management, we not just encourage them to perform well, but managers can get a clear idea about all the proctors performance. Also, predictive HR management helps manager to shut down unused proctor accounts and also estimating required proctors for the upcoming term.
3. Accurate Sign-in: To ensure security, it is very important to preserve exact timing of guest sign-in. And also to retrive the guests being signed quikly is very important. The new system will provide access to all information very intuitevely.
4. Go Green : The system will eliminate need of papers and will store everything online. And thus saving about 100,000 papers per annum. It also helps organizaion to save cost by not using papersheets.
5. Time Efficiency : The system allows everything remote and thus reducing a lot of time and avoid confusion drawn through a lot of conversation.
Business Case v 1.0
Page 19
5. COST BENEFIT ANALYSIS Cost benefit analysis in this project takes a different turn where mutual coordination of resources and the online website for daily work is crucial. Major costs are involved in the day to day work where most of the paper is involved and extra resources are kept for the printing, sorting and analyzing the content of all the sign-in sheets filled by the proctors. Also in this analysis some benefits are not cost related but work related which makes work easier and reduces the efforts which are required by each proctor and supervisor. Some of those cases are as follows 1) Making the proctor sign-in and sign-out online 2) Searching for the banned list based on the database content 3) Swiping the cards of the guest with any bar code. 4) Writing the detailed incident report and storing it in web based software for future use.
Business Case v 1.0
Page 20

These changes will save little cost in RSO new implementation but it will have a long term impact which will in turn change the functionality of the RSO.
Major cost savings are included though GoGreen initiative. This will allow eliminating all the paper work which currently involved being available online. Some of the major cost savings are shown below
First year costs (Action Action Type Description indicates anticipated savings) Purchase Webbased product and licenses Software installation and training Reduce Supervisors and Proctors staff by 4-5% Savings Cost Cost for IT group to install new software and for the training group to train all employees Optimization of the supervisors and proctors resource strength after implementing paperless system -$200,495.00 $10,000.00 Cost Initial investment for RSO Project $40,000.00
Business Case v 1.0
Page 21

First year costs (Action Action Type Description indicates anticipated savings) Managers/Super visors no longer required to go through each and every proctor sheet for finding mistakes Space and paper based system requires new papers and memos every week, and their maintenance Savings in cost to out-process exiting employee and recruit, Reduce employee turnover by 10% Savings hire, and train new employees by providing efficient training and resource planning is approximately $50,000 in the first year. -$50,000 Savings Work load and papers cost saved -$402,000 Savings 2-3 managers and 18-20 supervisors are required to invest almost every week almost more than 5 hours ($30 x 5) & ($15 x 5) to find the mistakes, write-ups, no-shows and probation related info for each and every proctor -$40,744.00
Business Case v 1.0
Page 22

First year costs (Action Action Type Description indicates anticipated savings) Net First Year Savings
$247,239.00
Based on the cost benefit analysis above we see that by authorizing the RSO Project, Northeastern University will save $247,239.00 in the first year alone. This represents a significant improvement in our operating costs and is a clear indicator of the benefit this project will have on the university which can be greatly used in increasing other security resources or new techniques.
Business Case v 1.0
Page 23

6. ALTERNATIVES ANALYSIS The following alternative options have been considered to address the business problem. These alternatives were not selected for a number of reasons which are also explained below:
Alternative Analysis Consider a different alternative COTS solution for web based solution Alternative Analysis System algorithms with auto shift assignment Alternative Analysis Outsource the security services to outside agencies
Reason for not selecting alternative Significantly higher costs and may not meet all the needs. Reason for not selecting alternative Might not be convenient for all the proctors to pick up a shift allotted to them. Reason for not selecting alternative It is better to give opportunity to the university students instead of paying and outsourcing the services.
Business Case v 1.0
Page 24

7. REQUIREMENTS DOCUMENT 7.1. EXECUTIVE SUMMARY This requirement document examines and shows the users and specifications in implementations of Residential Safety Office and how the GoGreen initiative is used to eliminate the entire paper based system and efficiently perform the daily critical and routine tasks. This migration of the system will be a big-bang approach where all the system are shifted to new implementation affecting following users and the depending services. The important function of the system is up all times and record accurate data to be stored securely. This online system is implemented targeting the following audience 1) Proctors 2) Supervisors 3) Managers Above audience mainly interacts with the system to record the data and operates with secondary components of the system.
Business Case v 1.0
Page 25

7.2. ASSUMPTIONS, RESTRICTIONS & LIMITATIONS Assumptions: 1) Servers are always up and running 24*7 2) All users know how to use the system functionality 3) All software functions will continue to function as required. 4) During daily work all proctors use the software to fill online sheets.
Restrictions: 1) All proctors must use the online sign sheet at all time. Usage of paper work is not allowed 2) Once the sheets are entered after shift no changes are allowed.
7.3. DATA FLOW
Daily sign in data
Check sign in data
Store sign in data
All day sign in info
Daily shift allocation
Check proctor availability
Assign shifts to proctors
Stations with shifts Allocation
Business Case v 1.0
Page 26

7.4. CUSTOMER W ORKFLOWS 7.4.1. AS-IS BUSINESS USE CASES AND ACTORS The Business use case depicts the big picture of the business processes (business use cases) that will be modified or replaced with the RSO project. The actors involved with each process are also shown.
Figure 7.4.1-1: Business Use Case Diagram
Business Case v 1.0
Page 27

7.4.2. TO-BE USE-CASES AND ACTORS The RSO functional use case below shows all use cases and actors involved in the RSO project. The box represents the scope of this project. The ovals inside are the different use cases sequence of actions that a system performs by interacting with the actors. The actors involved with the use cases could be the human beings, other system or pieces of hardware.
Figure 7.4.2-1: Actors Generalization and Functional Requirements (Use Cases) Diagram
Business Case v 1.0
Page 28

Actors are user types that represent certain behavioral patterns and are responsible for different operations with different sets of authorities. They represent the customer goals, to be achieved by means of the product. The actor could be a person, another system, a piece of hardware that interacts directly with the system. Each actor participates in at least one use case or coherent set of use cases to accomplish an overall purpose.
Actor proctor
Background and Skill Set Perform majority tasks in system and lower in hierarchy
Goals Monitor Daily activities in RSO and note them
supervisor
Perform admin tasks and middle in hierarchy
Track proctors and stations activities
Online workflow system
Software that acts as middleware between proctor and supervisor
Gather and maintain data, perform different functions on data and generate reports
Use-cases are collections of scenarios about system use, where each scenario describes a sequence of events. Each sequence is initiated by an actor or by passage of time. The result has to be something of use either to the actor who initiated or to another actor.
Use-Case ID RSOUC1 RSOIUC2 RSOUC3
Actor Proctor Supervisors System
Brief Description Daily Activities including filling sign in sheet, check in/out Daily monitoring activities and station reports Different report and shift generation
Business Case v 1.0
Page 29

7.5. BUSINESS AND FUNCTIONAL REQUIREMENTS 7.5.1. P APERLESS SOLUTION We need to develop paperless solution for recruitment process. o The solution will allow students to submit the application form online. o The system will allow students to access their training materials online. o The system shall allow students to give their exams online and view their results. Provide a paperless solution for daily summary work written by proctors and supervisors o The solution will allow Proctors to submit the sign in sheets online. o The system shall allow Proctors to view the history of summary work written Previously. o Supervisors will be able to view the summary work written by proctors. Define a paperless solution for memos and write-ups. o The solution will allow supervisors to submit memo online. o Proctors will be able to view the memos from the system. o Supervisors can submit write-ups about the proctors online through the system. o Proctors can view their corresponding write-ups online. o Proctors can view centralized list of guest and banned list entries.
7.5.2. EFFICIENT SHIFT AND BREAK MANAGEMENT Provide shift and break distribution through centralized system.
o Workstations are allocated to proctors while picking the shifts. o Break times are logged in to the system by proctors and supervisors.
7.5.3. SHIFT ALLOCATION o Develop a scheduling process which will prevent shift conflicts and swap board blocking. o The system should implement algorithm which will prevent shift conflicts and swap board blocking. o Easily view schedules for individual Proctors or the entire Proctors for the day, week, and month.
Business Case v 1.0
Page 30

o Personal Dashboard for the proctors to see their current days schedule, assigned Work Orders, and to dos ... The personal home page is designed to help them manage their schedule and it is unique to them. o Define a solution which will allow proctors to manage their shift allocation online. o Securely access the solution from anywhere, to quickly create and publish schedules. o Notify the proctors by email and text messages when schedule is published. o Control what proctors can see and do online using their own ID, view schedules, enter work time preferences, trade and pick up shifts, request time off and send messages, and much more. o Proctors will be able to pick their shifts online.
7.5.4. HR MANAGEMENT o Supports the Tracking of Time and Attendance Reporting for Proctors. o Manage the employee shift allocation and no of hour worked by proctors and supervisors. o Better handling of emergency situations and disciplinary actions.
7.6. GENERAL REQUIREMENTS o Predict the future budget of the management using statistics. o Analyze revenue by seeing trends in increase or decrease of the proctors And use the data for forecast the future budget. o Develop the software which follows web accessibility guidelines. o View interactive and static maps of the university's main campus, as well as o Travel directions to Northeastern residence halls. o Use skip navigation that allows users go directly to the main content of the page.
Business Case v 1.0
Page 31

7.6.1. DATA STORAGE If the data are stored electronically, the data should be regularly backed up on disc; a hard copy should be made of particularly important data; relevant software must be retained to ensure future access, and special attention should be given to guaranteeing the security of electronic data. Protect systems and individual files data with login and passwords. Manage access rights (in the case of computer system administrators not involved in the project their access rights could be limited). Regularly update virus protection to prevent vulnerability of data. Limit physical access to equipment and storage media (for example, in the case of data stored on a computer using a stand-alone computer may be secure than a networked, computer). Accurate data removal from old hardware and certification that the data was removed. Ensure data recoverability in case of emergencies. Regularly update electronic storage media to avoid outdated storage/retrieval devices. Backup multiple copies in secured multiple locations. Encrypt files when wireless devices are used, and keep track of wireless connectivity to prevent accidental file sharing. Record date and time when a piece of electronic data was originally recorded to prevent alteration or manipulation at a future date.
7.6.2. DATA DE-IDENTIFICATION Data not to be De-identified 1. Details of proctor on shift 2. Details of supervisor on shift 3. Details about RA on shift 4. Working hours of proctors, RAs and supervisor

7.6.3. DATA VALIDATION Identify duplicate records and merge or group together related information to get a unified view for business. Allowed character checks that only expected characters are present in a field. For example a numeric field may only allow the digits 0-9, the decimal point and perhaps a minus sign or commas. A text field such as a personal name might disallow characters such as < and >, as they could be evidence of a markup-based security attack. An e-mail address might require at least one @ sign and various other structural details. Consistency checks fields to ensure data in these fields corresponds, e.g., If Title = "Mr.", then Gender = "M". Data type checks the data type of the input and give an error message if the input data does not match with the chosen data type, e.g., In an input box accepting numeric data, if the letter 'O' was typed instead of the number zero, an error message would appear. Format or picture check Checks that the data is in a specified format (template), e.g., dates have to be in the format DD/MM/YYYY. Regular expressions should be considered for this type of validation. Logic check Checks that an input does not yield a logical error, e.g., an input value should not be 0 when there will be a number that divides it somewhere in a program. Presence check Checks that important data is actually present and have not been missed out, e.g., customers may be required to have their telephone numbers listed. Range check checks that the data lie within a specified range of values, e.g., the month of a person's date of birth should lie between 1 and 12.
Business Case v 1.0
Page 33

7.6.4. DATA AND USER ACCESS Object-Level Security has to be set to limit proctors from viewing timesheet approval sheet of manager. Supervisor should see data related to proctor, RAs and residents. Field-Level Security should be set for proctors when they are viewing banned list. Record-Level Security has to be set for proctor details. Each Proctor s hould be able to view only their personal information.
7.7.
AUDITING
Software Quality Assurance Audit should assess technical quality, form and function with the aim of improving aspects such as ease-of use, reliability, security and performance.
Software Compliance Audit should audit, the type that can produce anxiety, measures softwares level of compliance with regulatory mandates. A body outside of the company such as an industry watchdog or government regulator should conduct compliance audits.
Software Licensing Audit can be audited as part of Software Asset Management or Risk Management practices to determine where the software is distributed and how it is used. A license audit may be required to impose greater controls or find cost savings. The audit may seek to enforce software copyright protections. It can be mandated by the courts as part of a legal dispute. It can be ordered by risk managers who seek to determine the organizati ons level of exposure from continued use of the software.
7.8.
USABILITY
The system should be understandable, learnable, operable and attractive. Understandability

Interface elements (e.g. menus) should be easy to understand For a walk up and purchase or use system, the purpose of the system should be easily understandable
Business Case v 1.0
Page 34

Learnability

The user documentation and help should be complete The help should be context sensitive and explain how to achieve common tasks The system should be easy to learn
Operability

The interface actions and elements should be consistent Error messages should explain how to recover from the error Undo should be available for most actions Actions which cannot be undone should ask for confirmation The system be customizable to meet specific user needs A style guide should be used
Attractiveness
The screen layout and color should be appealing
7.9.

RELIABILITY
Software reliability extends across the entire development cycle. Be focused on how services are implemented and look for possible problems within the application.
Developers and operations staff should be properly trained in architecture and lifecycle management practices. Create a team culture where reliability is considered critical. Training and education should be provided where possible.
Use a Robust Operating System. For example, Windows servers often contain the following features Workload Balancing, Storage management, Memory Protection, Diagnostic and Recovery tools, Installation protection, etc.
Remove Failure Points from the Application Design All mission-critical data should provide monitoring data. Invest in Quality Software Engineering Processes Coding standards and programming practices should be shared across the business.
Business Case v 1.0
Page 35
Completed source code should be reviewed by peers for correctness, performance, reliability issues
The use of a consistent, repeatable, formal software development method always leads to more reliable systems.
7.9.1. P ERFORMANCE 95% of ALL visible pages for normal customers respond in 8 seconds or less , including infrastructure, excluding back ends. The software must support 8000 customers which will on a busy day generate 4500 customer interactions. The System should have downtime of maximum 88 hours (i.e. 1 % downtime) in a year. Response for user login must be no greater than four seconds throughout the day, with fewer than 3.4 errors per million transactions.
7.9.2. SUPPORTABILITY The Customer Advisor Help desk will support users of from 09:00 to 17:00 daily. The ability to change the system to deal with additional international conventions such as languages, or number formats, styles should be done. The average time needed to port the application from Internet Explorer to Netscape Navigator shall not exceed 6 person weeks. The MTTR shall be 1 day averaged over a 1 year.
7.9.3. SYSTEM AVAILABILITY Redundancy engineering is used to create systems with high levels of Availability. The system should be 99% available.(i.e.)7.2 hr. outage in a month
Business Case v 1.0
Page 36

7.10. INTERFACES The server module must integrate with a dbms through the java database connectivity (JDBC) interface. The server must run within a web server available for windowsnt, using dynamic content technology (e.g. jsp, cgi/Perl and cold fusion).
7.10.1. USER INTERFACES Ensure compatibility with the High-Contrast option. Use text fields (usually with a label) when the user may type in anything they want. use lists when there are many fixed choices (too many for radio buttons); all choices visible on screen at once use combo boxes when there are many fixed choices; don't take up screen real estate by showing them all at once use a slider or spinner for a numeric value
7.10.2. HARDWARE INTERFACES System should be implemented in a hardware-independent fashion and should not rely on any particular hardware interfaces expect for the power. The computer system must be able to be plugged into a power source. While this may seem obvious, power is not common at all before the residence hall.
7.10.3. SOFTWARE INTERFACES The System should use oracle database to save the proctor information, write ups, memos and more. To implement the project we have chosen Java language for its more interactive support. Since this is a web based project, System should run in all type of browsers without major changes.
Business Case v 1.0
Page 37

7.10.4. COMMUNICATION INTERFACES The new system will transfer data, which requires an Internet connection. There are alternatives to Internet connectivity, but due to time constraints we will make the assumption that the resident hall has Internet. When the "proctor" user class is included, user should allow communicating via standard email and via the World Wide Web. No other communications interfaces are mandated.
7.10.5. DATA MIGRATION INTERFACES AS/LIDB-AS/LIDB Data Migration Interface is used in migration of data from existing database to new database. It Support for descriptions, format, and encoding rules for two new line elements (data items), and to add them to the aggregate of the logical data model and associated requirements.
7.10.6. P URCHASED COMPONENTS The System is developed in Windows platform. The System needs oracle database server and web application server to run. All these components must have a warranty with legal terms and issues.
7.10.7. LICENSING REQUIREMENTS In order to use the system, it should be licensed. Password must be protected, only authenticated users can operate the system. The terms and conditions of software licenses can vary considerably. It is the responsibility of each University organization, staff member, to understand and adhere to software license requirements. If you are ever in doubt regarding the appropriate use of a software product, please ask us, or the software vendor/manufacturer. Individuals who purchase software should do so in accordance with their purchasing rules. When you purchase software from Software Licensing, please be prepared to provide the following information:
Business Case v 1.0
Page 38

Your University Network ID (UNID) and password. Your organization name or ID, or the organization name or ID of the organization that you are purchasing for. The name of the person within your organization who is responsible for the technical operation of the software that is being purchased (if not you). The name of the person within your organization who is responsible for maintaining software records. If you do not have purchase authority, the name and email address of the person who will authorize the transaction. Youre purchasing card or campus order information.
Software may be delivered in different ways. Some software products will be available to download from the Software Licensing web site provided the license allows downloads and we have the capacity to support the download. Software may be picked up at our office or delivered via campus mail. Prepare to be flexible, as available delivery methods will vary by product.
7.10.8. LEGAL , COPYRIGHT AND OTHER N OTICES These are terms and conditions set forth the rights being licensed to the customer for use of this application. These rights are the only rights the customer has for usage of this software. If in any event the customer does not agree to the terms and conditions or violate the rights, they cannot use the software. There is 1 year of limited warranty given under this terms and conditions. By installing the system, the customer agrees that this terms and conditions is a legally binding and valid contract, agrees to abide by all of the terms and conditions, and further agrees to take all necessary steps to ensure that the terms and conditions are not violated by any person or entity under customers employment. Licensor grants this license software to solely use by the customers company.
Business Case v 1.0
Page 39

7.10.9. DOCUMENTATION REQUIREMENTS
Business Case
The purpose of the Business Case is to justify the project and provide costs versus benefits details
Project Brief Project Initiation Document Contract
Provides a brief overview of the project, its scope and objectives. Provides an outline of the project, its scope and objectives. It goes into more detail than the Project Brief Used to obtain agreement from the Project Sponsor and Budget Holder to start the project
Customer Acceptance Form Quality assurance planning
Used to obtain agreement from the Project Sponsor and Budget Holder that the project has completed This document tracks the quality standards your project deliverables will have to align to. These may typically include product testing approach and tools, quality policies, quality checklists, deviations definitions, quality metrics, product defect severity grades, acceptance criteria, cost of poor quality, etc.
Project Progress Report
Provides status updates whilst the project is in progress
Project Closure Report Produced at the end of a project to indicate the outcomes and if and when a post implementation review will take place User guide commonly known as a manual, is a technical
communication document intended to give assistance to people
using a particular system.[1] It is usually written by a technical

writer, although user guides are written by programmers,
product or project managers. Lessons Learned Report (also survey) To provide details of all the things that went wrong in the project. Useful to learn from for future projects
Business Case v 1.0
Page 40

7.10.10. USER ACCEPTANCE TEST STRATEGY
The following are tasks and roles that team members will play for UAT: Prepare Test Plan Stage Data Provide help to the UAT users Create UAT user accounts Make system available Log and resolve issues and provide status. Prepare Test Plan Create test scripts for Program and Solicitation setup. Responsibility: Nisha Pepsi Selvarajan
Create Load Runner scripts for Performance testing of Application Responsibility: Kaustubh Pathak
Create UAT Test Scenario test cases Responsibility: Stage Data Configure Programs Responsibility: Pratik Zingade Fenil Gandhi
Configure Solicitations Responsibility: Pragati Dhavaleshwar Initial Review Peer Review: Kaustubh Pathak Application Review: Kaustubh Pathak

7.11. USE CASES Introduction
Use Case Name Application for proctor position Primary Actors Student
Use Case ID UC-1000
Date Created 04/18/2013
Created By RSO Team
Secondary Actors Manager
Use Case Name Responsibility of proctor Primary Actors Proctor
Use Case ID UC-1001 Secondary Actors Manager Supervisor
Created By RSO Team
Use Case Name Responsibility of supervisor Primary Actors Supervisor
Use Case ID UC-1002
Created By RSO Team
Secondary Actors Manager Proctor
Business Case v 1.0
Page 42

Use Case Name Responsibility of manager Primary Actors Manager Secondary Actors Supervisor Proctor Use Case ID UC-1004 Date Created 04/18/2013 Created By RSO Team
Use Case 1: Student Student: Students of northeastern university are the only once who are eligible to apply for proctor position. They are the most basic users of the system. They will be accessing system for
Sign Up: The NEU students need to create an account using their husky Id to create a new RSO account. They need to have an account in order to apply for any position.
Login: The students are required to login to system before they can apply for proctoring. Applying for proctor position: Submit resume, fill up the application form. Check application status: They can check whether their application is accepted for interview, Interview results, Test result and job start date
Check application deadlines: They can get a brief idea regarding when RSO will be accepting the applications and what are the deadlines for that. Schedule Interview: Student will be allowed to pick up a slot for his interview from the available slots.
Refer Learning Material: Students wont require taking physical lecture anymore. They will go through all necessary information directly from the web-portal, which will be helpful for their test.
Business Case v 1.0
Page 43

Give Online Test: Students can give test online. It will be a time based MCQ test, which is necessary to pass in order to become a proctor. The system will prevent student to navigate during exam. Test Result: The test will be evaluated instantaneously giving students their result at the end of the test.
Use Case 2: Proctor Proctor: The main responsibility of a proctor is to monitor students and their guests entering the dorm. Proctors are required to report to RSO if anything goes wrong. They also help residents in case of any lockouts or emergency.
They will be accessing system for SHIFT MANAGEMENT 1. Provide Availability: Proctors can give their availability for next shift release 2. Pick Up Shift: Proctors can pick up shift from the swap board 3. Drop Shift: Proctors can drop their shift, which will be available for others to pick up. Unless someone else picks it up, the same proctor will be responsible for the shift. 4. Exchange Shift: Proctors can exchange their shifts safely w/o interference from other proctors. They just need to know their user ID.
WORKSTATION MANAGEMENT 1. Workstation assignment: They can get their workstation by singing into the system. The system will randomly give the proctor his workstation for the current shift. 2. Remote Swipe In/ Swipe Out: the proctors will be considered as swiped in when they login from the computer at workstation. 3. Guest Sign-In: Proctors can write down all guests for a resident. This system automatically detects if a banned list person is trying to get signed-in and thus improving reliability. 4. Banned List: The list of all the people banned from dorms.
Business Case v 1.0
Page 44

5. Start-Stop Break: When a break starts for a proctor, the proctor who is giving breaks just needs to sign in and out to register the break timings. This will avoid any confusion and all the break timings get stored in the system. 6. Incident Write Up: To provide a better incident management, the system stores all the incidents in database which are required to be filled out by proctors in case of any incident. 7. Refer Memos: Proctors can also refer to any memos at e particular station by going through this feature 8. Lockout request: The proctors can now directly page RA from the system. He also needs to enter the residents information so as to keep record.
PROCTOR PERFORMANCE PROFILE 1. Look up Write up & Commendable notes: Proctors can easily access their write-ups and commendable given by their supervisors. 2. Appeal Write Up: They can also appeal for any write up if they want to. This will improve the transparency of write-ups and appeals throughout the RSO. 3. Refer Training Material: Proctors can still refer any material if they find something confusing.
ACCOUNT MANAGEMENT 1. Notification Management: They can manage their notifications regarding any shift available and etc. 2. Apply for supervisor: They can directly apply for supervisor in case if any opening.
Business Case v 1.0
Page 45
Use Case 3: Supervisor Supervisor: The main responsibility of a supervisor is to ensure proper working of each workstation by assigning proctors and monitor their activity. They also provide a gui deline to all the proctors during current shift.
They will be accessing system for SHIFT MANAGEMENT 1. Provide Availability: Supervisors can give their availability for next shift release 2. Pick Up Shift: Supervisors can pick up shift from the swap board 3. Drop Shift: Supervisors can drop their shift, which will be available for others to pick up. Unless someone else picks it up, the same proctor will be responsible for the shift. 4. Exchange Shift: Supervisors can exchange their shifts safely w/o interference from other proctors. They just need to know their user ID.
WORKSTATION MANAGEMENT 1. Look-up for no shows: supervisors are required to ensure that each workstation is assigned at least one proctor. He needs to check this before half an hour earlier than the shift. It is supervisors responsibility to ensure stand-by proctors in case of a no-show. 2. Assign Shift/Station: The supervisor has authority to directly assign shift and workstation to a particular stand by proctor. 3. Breaks Log: the supervisor needs to ensure that all the breaks for all station are running as per schedule and no one has taken more time than allotted maximum time.
INCIDENT MANAGEMENT 1. Report Incident: The supervisor can report any incident occurred directly from this system. The retrieval and search of past incidents also become quite easy through this online database.
Business Case v 1.0
Page 46

2. Give Commendable and Write-up: supervisors can directly give write ups and commendable to proctors and provide specific reasons for that as well. Upon receiving any write-up or commendable, proctors get a notification. 3. Add NUPD enter-exit info: Supervisor can easily keep track of NUPD entering and exiting from a specific station. The proctors still need to inform supervisors by calling so as to maintain integrity. 4. Go through lockout logs: Supervisors dont need to call RA on duty in case of lockout; proctors directly do this by sending a lockout request through their portal.
MISCELLANEOUS 1. Notification Management: They can manage their notifications regarding any shift available and etc. 2. Refer Training Material: Proctors can still refer any material if they find something confusing.
Use Case 4: Manager Manager: Manager is responsible to ensure sufficient and proper workforce and maintain security of all the dorms of Northeastern University.
They will be accessing system for
HR MANAGEMENT 1. Check for proctors needed: The system connects with Northeastern students portal in order to get an exact number of students who will be working in the next semester by eliminating users who are graduating or will be going on a co-op program. Thus, it not just disables all unused accounts, but also gives an exact idea regarding how many proctors RSO need to hire. 2. Go through sorted applications: Rather than going through each application, the portal sorts all the applications according to their eligibility and interests. Thus, giving managers a better list of applicants to be interviewed.

3. Schedule Interview: The manager is supposed to interview before hiring any candidate and the portal provides an easy way to schedule interviews with applicants. The manager just need to fill up his availability and a notification will be sent to all sorted applicant automatically. 4. Grant Privileges: After interview, if the applicant is hired for job, manager can directly grant his account from here so as to give him proper privilege of proctor or supervisor.
WORKSTATION MANAGEMENT 1. Update banned list and memos: The main responsibility of manager is to ensure updated banned list and provide memos at respective stations. Manager can update both banned list and write up memos for each station through the system. It also helps to keep track of all the memos for future reference.
QUALITY MANAGEMENT 1. Review incident: The manager is responsible to go through each incident occurred so as to ensure the security of all dorms. He can go through all incidents directly with this portal. 2. Review write-up: In case any proctor appeal against any write-up given by supervisor, manager can directly go through his appeal from the system and take decision based on the appeal. 3. Review proctor/supervisor performance: upon many write ups against any proctor or many complaints against supervisor, the manager can easily review his performance by going through his profile built based on all his write-ups, no-shows, commendable notes and even incidents reported by him. This gives an index for manager so as to decide whether a proctor should be continues or should be probated. 4. Probate proctor/supervisor: The manager can directly probate a proctors account for a specific amount of time. The system automatically notifies the proctor/supervisor.
Business Case v 1.0
Page 48

MISCELLANEOUS 1. Update training material: The manager can directly update the training material referred by everyone in case of any confusion. 2. Send notification: The system allows manager to send important notification, post deadlines directly from the system.
Business Case v 1.0
Page 49

8. HIGH LEVEL SYSTEM OVERVIEW:
High level system overview diagram to present complete picture
Business Case v 1.0
Page 50
9. DIAGRAMS AND PROCESS FLOWS: Online application system
Business Case v 1.0
Page 51
Business Case v 1.0
Page 52
Business Case v 1.0
Page 53
Business Case v 1.0
Page 54
Business Case v 1.0
Page 55
Business Case v 1.0
Page 56
Business Case v 1.0
Page 57

10. USER INTERFACE SCREENSHOTS
Business Case v 1.0
Page 58
Business Case v 1.0
Page 59
Business Case v 1.0
Page 60
Business Case v 1.0
Page 61
Business Case v 1.0
Page 62
Business Case v 1.0
Page 63
Business Case v 1.0
Page 64
Business Case v 1.0
Page 65
Business Case v 1.0
Page 66
Business Case v 1.0
Page 67
Business Case v 1.0
Page 68
Business Case v 1.0
Page 69

11. REPORTS General The header and the footer are same for all the reports generated. The font size used will be 12 and the font used is Calibri (Body) for all the reports. R 1.1. Report Header R 1.1.1. RESIDENTIAL SAFETY OFFICE NORTHEASTERN UNIVERSITY.
R 1.2. Report Footer R 1.2.1. <NAME OF THE REPORT>
R 1.3. Page Header R 1.3.1. RESIDENTIAL SAFETY OFFICE NORTHEASTERN UNIVERSITY.
R 1.4. Page Footer R 1.4.1. <NAME OF THE REPORT>
Report 1 R 2.1. Effort Summary Report - Effort reporting is a federal requirement for certifying that the effort charged or cost-shared to each award has actually been completed. Non-compliance with this requirement has resulted in audit disallowances and significant fines to several large research universities. R 2.1.1. R 2.1.2. Effort Summary Report Effort is defined as the amount of time spent on a particular activity. It includes
the time spent working on a sponsored project in which salary is directly charged or contributed (cost-shared effort).Individual effort is expressed as a percentage of the total amount of time spent on work-related activities (instruction, research, patient care, administration, etc.) for which the University compensates an individual. Effort reporting is the mandated method of certifying to the granting agencies that the effort charged or cost shared to each award has actually been completed. R 2.2. Sample
Business Case v 1.0
Page 70
Report 2 R 2.3. Monthly Turnover Report- A measure of how quickly a fund turns over its holdings during the year. A highly active fund will have a high annual turnover. It is equal to the dollar transaction volume of the trades in one year divided by the total portfolio size, expressed as a percentage.
R 2.3.1.
Monthly Turnover Report
R 2.4. The report includes the following fields: Code Pulled from the monthly history file for the position. Beginning Period Number of Positions The total number of position full-time equivalent (FTE) values for the beginning date and code, pulled from the monthly history file based on the begin date entered. Beginning Period Number of Vacant Positions Total vacant positions for the beginning date and code, pulled from the monthly history file, based on the begin date entered. Beginning Period Percentage of Vacant Positions Number of vacant positions divided by the number of positions and multiplied by 100, pulled from the monthly history file, based on the begin date entered. Ending Period Number of Positions The total number of position FTEs for the ending date and code, pulled from the monthly history file, based on the end date entered.
Business Case v 1.0
Page 71

Ending Period Number of Vacant Positions Total vacant positions for the ending date and code, pulled from the monthly history file, based on the end date entered. Average Number of Positions Beginning number of positions plus the ending number of positions divided by two. Turnover Percentage The number of separations divided by the average number of positions, multiplied by 100.
Sample
Business Case v 1.0
Page 72

12. APPENDICES A A.1. RSO: RSO in these documents refers Residential Safety Offices whose primary responsibility is access control of residential halls. A A.2. Data: Data in this report includes information about proctors, supervisors, working hours of proctors and supervisors, information related to residents of the building, guest visiting the residents. A A.3. Swap board: Swap board in the application means the platform where proctors and view available shifts, pick up a shift and drop a shift.
A A.4. NUPD: NUPD refers to Northeastern University Police Department. A A.5. Write-ups: Write-ups are kind of warning for proctors when proctors violate the rules.
A A.6. Memo: Memos contain important information like access information, NUPD alerts, policies etc. and are updated every day.
A A.7. Banned List: Contains list of names whose entry into the building is restricted.
A A.8. Workstations: Stations or resident building where proctor has to do his/her duty.
A A.9. UNID: UNID stands for University Network ID.
A A.10. UAT: User Acceptance Test Strategy.
A A.11. MCQ test: Multiple choice questions test taken while a proctor is hired.
A A.12.No shows: When a proctor is allotted a shift and the proctor does not come to the shift then it is called no show.
Business Case v 1.0
Page 1

A A.13. Sign-in sheet: In this report sign-in sheet refers to a sheet where the details of the guests entering the building are written by the proctor.
13. REFERENCED DOCUMENTS Contractor Performance Measurement Data Analysis Techniques by The Defense Systems Management College, Fort Belvoir, Virginia (published January 1983) Summerville, Ian & Pete Sawyer. (1997). Requirements Engineering: A good practice guide. o West Sussex, England: John Wiley & Sons. U.S. Air Force Systems Command Guide to Analysis of Contractor Cost Data (published August 1979) Human Resource Management http://people.brandeis.edu/~molinsky/documents/Human%20Resource%20Management%20Eth ics%20and %20Employment.pdf
For creating website - www.wix.org For creating USE Cases www.creately.com
14. APPROVALS The signatures of the people below indicate an understanding in the purpose and content of this document by those signing it. By signing this document you indicate that you approve of the proposed project outlined in this business case and that the next steps may be taken to create a formal project in accordance with the details outlined herein.
Approver Name Robert O. Jose
Title Associate Dean and Director Department of Residential Life
Signature
Date
Ann Marie Regan
Director of Operations, Student Affairs
Business Case v 1.0
Page 2

Residential Safety Office Business Case

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Residential Safety Office Business Case

Hochgeladen von

Copyright:

Verfügbare Formate

Business Case

RESIDENTIAL SAFETY OFFICE (GOGREEN INITIATIVE) AT NORTHEASTERN UNIVERSITY

Residential Safety Office (GoGreen Initiative) Table of Contents

Residential Safety Office (GoGreen Initiative)

Business Case v 1.0

Residential Safety Office (GoGreen Initiative) 1. EXECUTIVE SUMMARY

Business Case v 1.0

Residential Safety Office (GoGreen Initiative)

Business Case v 1.0

Residential Safety Office (GoGreen Initiative) 2. BUSINESS CASE ANALYSIS TEAM

Name/Title Kaustubh Pathak Nisha Pepsi Selvarajan Pratik Zingade

Business Case v 1.0

Residential Safety Office (GoGreen Initiative) 3. PROBLEM DEFINITION

Business Case v 1.0

Residential Safety Office (GoGreen Initiative)

easy and supervisor will be able to record it accurately.

Business Case v 1.0

Residential Safety Office (GoGreen Initiative)

Business Case v 1.0

Residential Safety Office (GoGreen Initiative)

Business Case v 1.0

Residential Safety Office (GoGreen Initiative)

Business Case v 1.0

Residential Safety Office (GoGreen Initiative)

Residential Safety Office (GoGreen Initiative)

Target Date 01/21/2013 02/11/2013 02/18/2013 03/07/2013 03/24/2013 04/14/2013 04/20/2013

Business Case v 1.0

Residential Safety Office (GoGreen Initiative)

Register as proctor, supervisor. Login as Proctor/Supervisor.

Sprint 2 Feb 26-Mar 11

Submit and view memos, banned list, online sheets.

Sprint -3\ Release 1 Mar 12-Mar 25

Sprint 4 Mar 26-Apr 8

Business Case v 1.0

Residential Safety Office (GoGreen Initiative)

Business Case v 1.0

Residential Safety Office (GoGreen Initiative)

Business Case v 1.0

Residential Safety Office (GoGreen Initiative)

Business Case v 1.0

Residential Safety Office (GoGreen Initiative)

Total effort for the project

Business Case v 1.0

Residential Safety Office (GoGreen Initiative)

Business Case v 1.0

Residential Safety Office (GoGreen Initiative)

Business Case v 1.0

Residential Safety Office (GoGreen Initiative)

Business Case v 1.0

Residential Safety Office (GoGreen Initiative)

Business Case v 1.0

Residential Safety Office (GoGreen Initiative)

Business Case v 1.0

Residential Safety Office (GoGreen Initiative)

Business Case v 1.0

Residential Safety Office (GoGreen Initiative)

Business Case v 1.0

Residential Safety Office (GoGreen Initiative)

7.3. DATA FLOW

Daily sign in data

Check sign in data

Store sign in data

All day sign in info