Reference no: EM131324780

Assignment

Rules:

1. Answer all questions directly in this document including diagrams, images, etc. Please leave the questions intact. Submit only this single document please!

2. Object-oriented languages only.

3. No hand-written drawings.

Scenario

You have recently been hired at Huge Corporation, a defense contractor, as part of their software engineering team. This corporation has over 15,000 employees in the Delmarva region withseven different locations: New York, Massachusetts,New Jersey , Richmond, Washington D.C, Annapolis, and Hagerstown; the software engineering department is spread out over all seven locations and you will be assigned to Washington D.C. This defense contractor provides valuable services and products to boththe federal government and state government in the U.S., and also works with selected foreign customers as well.

Recently Huge Corp won a massive joint contract with LittlesCompany, a smallbut upcoming firm located in California that specializes intechnology which handles the processing of secure paperwork and payments for government entities. The contract is with the U.S. Department of Defense to overhaul theirancient, mostly paper-based system that handles purchasing for the DOD. The list of issues with the old system is endless but includes hard copies of all purchases made which must then be stored, a submission process requiring faxing of forms which must be firstprinted and filled out manually, and a ridiculously redundant approval process for any purchase over $1000 which is pocket change for the DOD. No one at the DOD really knows where the process originated however attempts to change it entirely have resulted in inter- and intra- departmental fighting mainly due to departments and individuals protecting their "turf" (aka jobs). No one wants to the person or department that is deemed redundant and replaceable by a computer or some type of automated process.

Your contract has an overarching goal of making the new system streamlined, efficient and most definitely, 100% electronic. It has been "unofficially" relayed to you from top-level DOD management that they have finally acknowledged that they have somewhere around 2-3 people doing the job of what one person or a computer could do. The DOD has stated they want the contract to be implemented in three main parts:

Part 1: Documentation of the current purchasing process. These documents are expected to be "living" documents that may change.

Part 2: Creation of a new purchasingprocess which will be approved by top-level staff at the DOD.This process must also be documented in a fashion which supports modifications as needed. The DOD understands that there may be some revisions over the years.

Part 3: Upon approval, HUGE Corp, will coordinate with Littles Company to implement the new purchasing system.

Part 1 and 2 are expected to be the most challenging as it is extremely difficult to accurately document a process used at such a large entity when every employee is trying to justify their job regardless of it is redundant or even needed. The DOD has estimated that the paper-based storage system of records alone keeps 30-50 people employed; moving to the new system will most definitely put many people out of work. In an attempt to alleviate some of the fear, the DOD has stated that they will place at least 50%of the cut positions, and will provide full-salary along with job-search assistance to those employees who positions are permanently cut.

To add further complexity to the project the DOD has stated that they would like to see periodic deliverables meaning they do not want to wait until the end of each Part or the end of the contract to see the finished products. They are fed up with the system and have stated that it is vital to "get it right this time as they are wasting too much money."

Part I-

Using the situation described above write out all requirements and use cases. you may make your own assumptions. If you chose to make your own assumptions they MUST be thoroughly documented and explained at the beginning of this document under a section that is clearly labelled "Assumptions". Do not just write down random requirements or use cases with no explanation. I also expect that any assumptions adhere to the rules above.

Part II-

Use the OO Identification trickto generate an end result table like below for the situation described at the beginning of the document.

Lay out your class diagram with details. (Include properties and methods). Provide a description for each class. Explain why and how your design follows the guideline of "loose coupling and tight cohesion". Do not just provide a definition for coupling/cohesion - explain how your design adheres to the rule "loose coupling and tight cohesion".

Lay out a high level architecture diagram. It should capture how your product will be structured. Briefly explain each piece.

Create a sequence diagram(s) that encompasses the system functionality.

PART III-

Compose a single essay of approximately one page, single-spaced that addresses the following:

- Which process or combination of processes your team should follow and why. Make sure to justify WHY your choice(s) is/are appropriate for this particular situation, and not just provide a definition. Simply providing a definition will result in an automatic deduction of 7%. (10%)

- At least five risks and how to mitigate each risk.

- How you will support the concept of continuous integration on such a large team that spans across multiple locations and companies? How will you control changes to both documentation and code? Be specific and detailed.