Sr. Manager

In: Business and Management

Submitted By Roopesh25
Words 4167
Pages 17
Executive Summary The Federal Government’s current Information Technology (IT) environment is characterized by low asset utilization, a fragmented demand for resources, duplicative systems, environments which are difficult to manage, and long procurement lead times. These inefficiencies negatively impact the Federal Government’s ability to serve the American public. Cloud computing has the potential to play a major part in addressing these inefficiencies and improving government service delivery. Amtrak, one of top client for Lockheed Martin is facing similar challenges to reduce the cost of IT infrastructure maintenance in their data center operations. Lockheed Martin has a unique cloud model which is focused on providing solutions as a service based on a mission focused approach to secure cloud delivery. They have successfully implemented cloud services for many clients. This study specifically focused on implementing the cloud computing strategy and services provided by Lockheed Martin that can significantly help Amtrak to provide highly reliable, innovative services in an efficient manner and at the same time reduce IT operating costs. Interviews were conducted with key business stakeholders at Amtrak and also with some of the IT project team members to learn about the existing data center model set up, data storage, and the hardware and software applications that are currently used. Interviews were also conducted with employees to understand the perception of cloud system infrastructure services and how it can help them. This report concludes that Lockheed Martin is deeply involved in delivery of cloud computing services to his clients and will provide a unique cloud computing framework that can benefit Amtrak. The challenge at Amtrak is that even though they ready for changes in the infrastructure management but they are unaware of the value of cloud…...

Similar Documents

Sr-Rm

...SR-rm-022 Part Three Jesca Malabed BSA375 January 3, 2013 Dan Speck SR-KF-013 Part one Riordan Manufacturing is a global plastic manufacturer. The annual projected annual earning is $46 million and employs 550 people. Riordan manufacturer is a fortune 1000 enterprise. Riordan produced plastic beverage containers, custom plastic parts, and plastic fan parts and their major customers are automotive parts manufacturer, aircraft manufacturer, the Department of Defense, beverage makers and bottles, and appliance manufacturer. Riordan has four offices, Georgia, Michigan, China, and the main head quarter in San Jose (University of Phoenix,  2012). HRIS “The company’s HRIS (Human Resources Information System) is part of the financial system package that was installed in 1992. The system keeps track of the following employee information: * Personal information * Pay Rate * Personal exemptions * Hire date * Seniority date * Organization information * Vacation hours (University of Phoenix,  2012). Key Stakeholder The key stakeholders for Riordan Manufacturing are the Finance and Accounting, and Sales and Marketing user. The analyst needs to gather requirements from this two department because if the Finance and Accounting system is change, the Sales and Marketing system needs to be informed. For example the Finance and Accounting change a customer’s information, Sales and Marketing needs to know the new information so Sales and Marketing can...

Words: 1347 - Pages: 6

Hostel Maangement Srs

...Requirements Specification (SRS) System requirements are expressed in a software requirement document. The Software Requirement Specification (SRS) is the official statement of what is required of the system developers. This requirement document includes the requirements definition and the requirement specification. The software requirement document is not a design document. It should set out what the system should do without specifying how it should be done. The requirement set out in this document is complete and consistent. USER REQUIREMENTS In this system we find the operations depending on the Different end users. Functionality are listed below: Administrator: 1. Admin is the only user who can log in to the system, who has privileged access to the whole database. 2. He can view, modify or delete any kind of data 3. He can generate various periodic reports with regard to the whole database. 4. A unique password is given to the admin which can be used for availing the privileged access. 5. He can maintain the details of each branch’s details including warden’s and student’s details Student: 1. Student can view their information regarding fees, room and mess information. 2. Student can check the fine of them . 3. Student can pay the fine. 4. Students are also provided with user name and password for more security. Mess Manager: 1. The mess manager can see the data of the students. 2. The mess manager can check......

Words: 710 - Pages: 3

Sr Cuban

...(High; Medium; Low) and consequences of loss of service or a reduction in normal service levels. (Collaborative for Disaster Mitigation) www.sjsu.edu/cdm 8 CDM 2003 RLM 06/20/06 BIA Lessons Learned EXAMPLES – basic considerations Contents Part 1 – – Functional Criticality Assessment Key Business Processes/Functions Part 2 Part 3 Part 4 Part 5 Dependencies Impact/Maximum Downtime Critical Equipment & Resource Supporting Functions Mission Critical Records Network & System Requirements 9 CDM 2003 RLM 06/20/06 BIA Lessons Learned EXAMPLES- basic considerations Part 1 – Key Business /Functions/Processes Suggested 1st Step in BIA Process: For each Function within a business area (Department), have the Department Manager or higher identify and rate their respective area’s functional requirements. 10 RLM 06/20/06 BIA Lessons Learned EXAMPLES – basic considerations MISSION CRITICAL – the business cannot survive without it. URGENT – Important, and will result in some impact, but business will survive without it. NICE TO HAVE – Neither Critical nor Urgent. Everyone has a ‘wish list.’ 11 RLM 06/20/06 BIA Lessons Learned EXAMPLES – basic considerations Part 1 - Key Business Processes/Functions/Dependencies The following slide is a descriptive list of the organization’s key business areas (Departments), in order of importance to the business, together with a brief description of the business function/process and main dependencies: CDM......

Words: 3094 - Pages: 13

Manager

... Store managers Forecasting model Inventory in stores, past sales Requested shipment quantities for each reference and size Warehouse inventory Inventory in stores Demand forecasts Warehouse inventory Warehouse allocation team Optimization model Shipments Shipments that although the general problem just stated is not specific to fast-fashion retailing, we believe that several features that are specific to this retail paradigm (short product life cycles, unique store inventory display policies) justify new approaches. Indeed, Zara’s interest in this area of collaboration was motivated by its desire to improve the inventory distribution process it was using at the beginning of our interaction for deciding the quantity of each article to be included in the weekly shipment from the warehouse to each store (see Figure 1(a) for an illustration). According to that process, which we call the legacy process, each store manager would receive a weekly statement of the subset of articles available in the central warehouse for which he/she may request a shipment to his/her store. Note that this weekly statement (dubbed “the offer”) would thus effectively implement any high-level assortment decision made by Zara’s headquarters for that particular store. However, it would not mention the total quantity of inventory available in the warehouse for each article listed. After considering the inventory remaining in their respective stores, store managers would......

Words: 16085 - Pages: 65

Srs for Rto

...parts of vehicle. Out Scope: Unpredicted failures of functional parts of vehicle causing severe accidents. Benefits o To improve the efficiency. o Quickly find out information of vehicles. o To provide easy and faster access information of license holders. o To provide user friendly environment. o To reduce error during manual registration. o To complete registration during purchase of vehicle itself. 1.3 Definitions, Acronyms, Abbreviations SRS - Software Requirements Specification. GUI- Graphical User Interface RTO-Regional Transport Office 1.4 REFERENCES Appendix C: Generation of license 1.5 OVERVIEW Project Overview The following subsections provide the complete overview of the software specifications requirements documentation for the regional transport office. The entire SRS is documented in view of User and the following sub sections are arranged to give a complete outlook of the software, its perspective, features, system requirements and users know how it is. 2. Overall description 2.1 Product perspective The system is aimed to automate the major processes in the Regional Transport Office. · Registration of vehicle through online. · Fancy number selection of vehicles through online. · Issue of information’s about license, which include application ......

Words: 1356 - Pages: 6

Srs Doc

...Srs-Online Course Registration System Table of Contents 2. Introduction 1 2.1 Purpose 1 2.2 Scope 1 2.3 Definitions, Acronyms, and Abbreviations 1 2.4 References 1 2.5 Overview 1 3. General Description 2 3.1 Product Perspective 2 3.2 Product Functions 2 3.3 User Characteristics 3 3.4 General Constraints 4 3.5 Assumptions and Dependencies 4 4. Specific Requirements 4 4.1 External Interface Requirements 4 4.1.1 User Interfaces 4 4.1.2 Hardware Interfaces 4 4.1.3 Software Interfaces 4 4.1.4 Communications Interfaces 4 4.2 Functional Requirements 4 4.3 Use Cases 7 4.4 Classes 8 4.5 Non-Functional Requirements 9 4.5.1 Performance 9 4.5.2 Reliability 9 4.5.3 Scalability 9 4.5.4 Security 9 5. Analysis Models 9 5.1 Sequence Diagrams 9 5.2 Collaboration Diagrams (STD) 10 5.2 State-Transition Diagrams (STD) 11 5.4 ACTIVITY DIAGRAM……………………………………………………………………………………….15 5.5 DEPLOYMENT DIAGRAM…………………………………………………………………………………15 2. Introduction The Online Student Course registration system is automated system where the user can register the student for various courses. This is proposed for automating the student’s course registration. While the student joins any educational institution his admission is made on the basis of his previous records. The students who wish to the institution must be given with the available course details. The student is allotted with a seat in the institution based on the marks that he scored in the institution he......

Words: 338 - Pages: 2

Srs Template

...Index : Technical Specification Sections Finalised by SRS Commiittee for Restructured APDRP under 11th Plan Page-1 Section – G1 :: General Technical requirements Sl. No. Title Page No. / Section No. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 Introduction Intent of specification Scope of work Other Services and Items Specific Exclusions Utility’s Current IT Infrastructure Arrangement by the Contractor Software tools Warranty, operational guarantee and system reliability with ‘on-site’ support Annual Maintenance Contract Price Loading for Evaluation of Bids Payment terms Project synopsis Bid Schedule Basic reference drawings Spares Time schedule Implementation schedule Quality assurance plan Qualifying requirements 2 of G1 2 of G1 4 of G1 19 of G1 23 of G1 23of G1 23of G1 24 of G1 24 of G1 26 of G1 26 of G1 27 of G1 27 of G1 27 of G1 27 of G1 27 of G1 28 of G1 28 of G1 28 of G1 29 of G1 Page-2 Section – G2 :: Technical specification requirements for Application Packages Sl. No. Title Page No. / Section No. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 Part-A – Essentially Required by most Utilities for setting up an IT backbone for collection of baseline data, Energy Accounting / Auditing and establishment of Customer care centers Introduction System Functionality Module : Meter Data Acquisition Module : Energy Audit Module : New Connection Module : Disconnection & Dismantling Module : GIS based customer Indexing and asset mapping......

Words: 90558 - Pages: 363

Hms Srs

...Team One Approval 122 5.2 Team Two Approval 122 6 Supporting Information 122 Introduction The following subsections of the Software Requirements Specifications (SRS) document provide an overview of the entire SRS. 1 Purpose The Software Requirements Specification (SRS) will provide a detailed description of the requirements for the Hotel Management System (HMS). This SRS will allow for a complete understanding of what is to be expected of the HMS to be constructed. The clear understanding of the HMS and its’ functionality will allow for the correct software to be developed for the end user and will be used for the development of the future stages of the project. This SRS will provide the foundation for the project. From this SRS, the HMS can be designed, constructed, and finally tested. This SRS will be used by the software engineers constructing the HMS and the hotel end users. The software engineers will use the SRS to fully understand the expectations of this HMS to construct the appropriate software. The hotel end users will be able to use this SRS as a “test” to see if the software engineers will be constructing the system to their expectations. If it is not to their expectations the end users can specify how it is not to their liking and the software engineers will change the SRS to fit the end users’ needs. 2 Scope The software product to be produced is a Hotel Management System which will automate the major hotel operations. The first subsystem...

Words: 2464 - Pages: 10

Srs Document

...Requirements of Ambulatory Medical System 6.2 Non- Functional Requirements of Ambulatory Medical System 6.3 Real-time Ambulatory Medical System Performance 6.4 Design Constraints 1. Introduction 1.1 Purpose The software requirement specification document is specifically designed to delineate the boundaries of the Healthcare Information System design and functionality. Parties interested in this documentation would include but not be limited to the system owners, the system users, the project manager and the design team. 1.2 Scope of Document This document will identify the pertinent software products we will develop including a Host DBMS, JAVA software supported and web-based Patient, Physician, and Ambulatory Input/Outputs, and sensor driven inputs for real-time patient monitoring. The SRS will show that we will be utilizing SQL server and ASP for interfacing with the Input/Outputs as well as Java applets for the real-time acquisition of health data from remote sources. Finally, utilizing the security attributes of XML, XSL, and a secure socket layer in the protocol stack we hope to address the valid security concerns about the networking and transmission of confidential health care information. In addition to the specific design components of this software, this document will make clear the design team’s goals of creating value-added software......

Words: 4207 - Pages: 17

Sr Corporation

...MK609 - Marketing Case Analysis for SR Corporation: Decisions for an Emerging Technology October 7, 2009 Introduction SR Corp was formed in 1986 to develop and commercialize advanced speech recognition technology. The company's mission was to deploy a new generation of speech transaction technologies, products, and systems that could be easily integrated into telephone and computer networks. The company's goal was to become the leader in a new realm of human communications. SR Corp was financed by private investors. For the past eight years the company focused on developing its core technologies of large-scale speech recognition systems. SR Corp based their solution requirements on feedback from large companies in their target market segment. The solutions developed by SR Corp are targeted at three distinct niches within the telephony segment of the speech recognition market: • Fortune 500 corporations • Telephone companies • Telephone switch OEM's Each niche market provides both opportunities and risks. SR Corp products have shown to be much further advanced then the leading market research firms and industry experts expected at this point in time. The company also had several other advantages including: • Seven US and foreign patents with other pending that will be in force into the next century • SR Corp technology is different then AT&T and other larger competitors • The product and solutions are......

Words: 2245 - Pages: 9

Srs Doc.

...E-Store Project Software Requirements Specification Version Revision History |Date |Version |Description |Author | | | |SRS 1.0 |Group-1 | | | |SRS 2.0 |Group-1 | | | |SRS 3.0 |Group-1 | | | |SRS 4.0 |Group-1 | Table of Contents 1. Introduction 5 1.1 Purpose 5 1.2 Scope 5 1.3 Definitions, Acronyms, and Abbreviations 6 1.4 References 6 1.5 Overview 6 2. Overall Description 6 3. Specific Requirements 7 3.1 Functionality 7 3.1.1 Sell Configured to Ordered Products. 7 3.1.2 Provide comprehensive product details. 7 3.1.3 Detailed product Categorizations 7 3.1.4 Provide Search facility. 7 3.1.5 Maintain customer profile. 8 3.1.6 Provide personalized profile 8 3.1.7 Provide Customer Support. 8 3.1.8 Email confirmation. 9 3.1.9 Detailed invoice for customer. 9 3.1.10 Provide shopping cart facility. 9 3.1.11 Provide multiple......

Words: 2870 - Pages: 12

Srs Project

...CIS 339 May 4, 20124 System Request – SRS Project Project sponsor: Business Need: This project has been initiated to keep up with the high demands of increased enrollments and to allow students to handle their own registrations online using an Internet-accessible system. Business Requirements: Using an Internet-accessible system, staff should be able to work from any location that has an Internet connection and a web browser. Also, students should be able to self-register directly for their own classes. The functionality that the system should have is listed below: * Maintain records for students enrolled in the school * Maintain courses offered by the school * Maintain classes offered of these courses in the two modalities of online and face-to-face * Maintain student grades for the classes that they have completed Business Value: We expect that SRS will help to reduce the generation of the many errors in moving the paper form to the electronic registration filing. Also, SRS should help the staff to free up so they can complete other tasks allocated to them like staff development and training. Conservative estimates of intangible value to the company includes: * Increase in staff productivity * Reduce the use of paper registration forms * Reduction of errors due to the adding/dropping of classes Special Issues or Constraints: * The system should be in place for the next school semester registration * This......

Words: 500 - Pages: 2

Srs on Vrs

...Sponsor: Government of the Punjab Project Manager: Mr. Tahir Aziz KhanRenewal System (VVRS) 5 17. Make the system more reliable and unambiguous. Increase the efficiency and effectiveness of the registration process. Enhance the processing of vehicle registration system. Identify and track the vehicles in circulation. Make it possible to link vehicles with their rightful owners. Fight against registering stolen vehicles. Revoke registration of old vehicles that have been destroyed. Ensure that all vehicles are regularly inspected to determine if they are still fit to drive. Make vehicle owners accountable in case of unpaid registration taxes. Lower the cost of vehicle registration transactions Improve integrity of titling Reduce the number of uninsured vehicles Enhance security and improve vehicle safety Increase compliance screening process efficiency and accuracy Automates enforcement actions and violation processing for non- compliant vehicles and outstanding violations.Project Objectives 6 18. Deliverables 7 19. Organizational Hierarchy 8 20. Organizational Structure 9 21. The developers use this document while working through the different phases of Software Development Life Cycle (SDLC). Documenting and controlling the customer requirements is a prerequisite for using them, as the basis for planning, performing and tracking the software project’s activities throughout the SDLC. This Software Requirement Specification (SRS) will act as a template for......

Words: 1320 - Pages: 6

Srs for Gratuity Claims

...Content: Font Times New Roman and size 12 Intended Audience and Reading Suggestions This SRS document is intended for developers, professors/instructors and students for reviewing and monitoring the progress of the project. This document can be used for analyzing the requirements. The rest of the document contains the functional and non-functional requirements of the project. Product Scope This project allows authorized members to access their respective profiles with discretion and privacy. It can be used in various Private organizations across the globe and simplifies working of such. This project helps in maintaining the database of the Employees in any organization. The user can easily access the information anytime and can be kept safely for long period of time without any damage. References * SRS of “Web Publishing System” by Joan, Paul Adams, Bobby Baker and Charles Charlie, Version 1.0, April 15 2014 * http://en.wikipedia.org/wiki/Software_requirements_specification. * Idrus, Rozali, S., and Desa, H., (2009) ‘The development of web based claim system: Computer Technology and Development’. ICCTD ’09. International Conference pp.317 - 321. * www.sciencedirect.com Overall Description Product Perspective The following diagram describes the high level business process of A Gratuity Claims Processing System (GCPS). Creation and Maintenance of Employee Profiles The HR manager updates the database after an employee resigns or a project is completed The......

Words: 1856 - Pages: 8

Srs on Osms

...SRS ON ONLINE SCHOOL MANAGEMENT SYSTEM Software Project Lab-2 Title: Online School Management System Group Member: Nowrose Ashraf Supervisor: Emon Kumar Dey Lecturer Institute of Information Technology University of Dhaka Submission Date: 29th Mar, 2014 Contents Chapter 1 1 1.1 Introduction 1 1.2 Purpose 2 1.3 Goals 2 Chapter 2 3 2.1 Introduction 3 2.2 Identifying Stakeholders 3 2.3 Recognizing multiple viewpoints 5 2.4 Working towards collaboration 6 2.5 Common requirements 6 2.6 Conflicting Requirements 6 2.7 Final requirements 7 2.8 Conclusion 7 3.1 Introduction 8 3.2 Eliciting Requirements 8 3.3 Collaborative Requirements Gathering 9 3.3.1 Requirement elicitation through interview 9 3.3.2 Requirement elicitation through questioning 10 3.3.3 Record view 10 3.3.4 Observation 10 3.4 Quality Function Development 10 3.4.1 Normal Requirements 11 3.4.2 Expected Requirements 11 3.5. Case Scenario 12 3.5.1. Registering Online 12 3.5.2. Admission 12 3.5.3 Student database generation 13 3.5.4 Attendance sheet generation 13 3.5.5 Result sheet generation 13 3.5.6 Annual report generation 13 Chapter 4 14 4.1 What is usecase diagram? 14 4.2 Usecase Diagram 15 4.3 Activity Diagram and Swimlane Diagram 31 4.3.1 Activity Diagram 31 4.3.2 Swimlane Diagram 39 Chapter 5 47 5.1 Data Modeling Concept 47 ...

Words: 6864 - Pages: 28