Computer Science Department
Courant Institute of Mathematical Sciences
Course Title: Software Engineering Course Number: g22.2440-001
Instructor: Jean-Claude Franchitti Session: 11
Final Examination – The Whole Enchilada! Sell Your Solution
IV. Software Required
1. Problem Statements:
Problem scenario used below is for reference purpose only. You must apply the same general approach to provide a solution for your team project.
3-State Mining Co. are currently evaluating a number of competing bids to build a mine pump control system. They have assembled together their key business decision makers and chief architects to make a final decision with respect to purchasing a solution that will meet their requirements.
Assemble yourself into groups of 2 people (3-6 would be best!). You will represent the chief architects for your proposed solution. Give your company and proposed product a name. Your job is to “sell” the product to the customer by clearly outlining the functionality your architecture will provide and the non-functional capabilities your architecture will support.
You have 30 minutes to prepare your presentation. You are welcome to build a “best of breed” solution from the exercises you have completed in this workshop, or put together new ideas, its up to you!
3-State are a large mining company,
owning mining properties in
3-State have a classic “accidental infrastructure”. Over various tenures of CEO/CTO/CIO a number of different products have been bought “in house” driven by both technical and political issues prevalent at the time of purchase. As a consequence the following environments are licensed and supported by the organization.
Application Servers – Microsoft, IBM WebSphere™
Operating Systems – Solaris, Win2000/XP, OS X
Hardware – Mainframe, RS6000, AS/400, Wintel Servers, Apple OSX Servers
Databases – DB2, Oracle, Teradata
3-State have a variety of pump installations, but all conform to Federal Pump Standard THX-1138, that describes a common interface and protocol for control systems. Sensors and alarms are both inexpensive and widely available, but will need to be bought and installed as part of the installation of your system.
The following represents an agenda for each presentation:
(1) Executive Summary (2.5 minutes) – provide an overview of your proposed architecture, focus on key functional and non-functional characteristics. Outline the technical key benefits that your architecture will provide to the customer.
(2) Requirements (5 minutes) – lead the customer through the key use cases, by walking through the “architecturally significant” primary scenarios of selected use cases.
(3) Solution Architecture (10 minutes) – provide an overview of the following:
a. How your architecture will be partitioned e.g. 2 tier, 3-tier N-tier and the advantages of your choice
b. Justify any additional architectural patterns you have selected, outline the advantages they will provide within the customers current operating environment.
c. Describe the object model you have developed in all its glorious detail, focus (as an architect should) on the key external characteristics. Use class diagrams, sequence diagrams to illustrate your solution (these may be simply drawn onto paper and distributed to the audience as required)
d. The customer has stated that they are particular interested in “best practices” with respect to architecture, they want a solution that is both understandable and maintainable by their own IT teams (who will maintain the code base following delivery). As a consequence they are particularly interested in the best practices you have applied to reach your solution.
(4) Capabilities (5 minutes) – Describe the following “-ilities” of your architecture : Scalability, Extensibility, Maintainabilty, Flexibility, Validity….
(5) Technical Architecture (2.5 minutes) – what are the main hardware and software components of your platform?
(6) Process (2.5 minutes) – the customer has requested that an iterative development process be followed with the incremental delivery of functionality to the 3-state user acceptance test team.
a. What will you deliver in each iteration?
b. How long will each iteration take?
c. How many iterations will there be?
d. What technical risks are associated with each iteration?
e. What technical resources will be required in each iteration?
(7) Price – fold up a piece of paper, put down a figure and hand it to the instructor. Make sure that you have enough to cover your estimated costs, with money to feed and clothe your families.
(8) Questions (5 minutes) – prepare for some hard questioning from the instructor and your peers, defend your architecture!
After all the presentations all the participants should vote on who made the best presentation … give your hidden ballot (no hanging chads please) to the instructor who will announce the results. You may not vote for your own team!!!!!!!!!
Fill in the blank area for each field.
The sequence of the hardcopy submission is:
1. Cover sheet
2. Individual topic solutions as per agenda section
______________ Date: ____________
(last name, first name, username is SID)
Final Examination Assessment
o Assignment is neatly assembled on 8 1/2 by 11 paper.
o Cover page with your name (last name first followed by a comma then first name), email, and section number with a signed statement of independent effort is included.
o Individual topic solutions as per agenda section.
o File names are correct.
o Word document.
o Completeness of topic coverage.
o Appropriateness of comments.
Total points ___________________
Affirmation of my Independent Effort: _____________________________