https://www.google.com/contributor/welcome/?utm_source=publisher&utm_medium=banner&utm_campaign=2376261057261409

Search This Blog

Search with our Site

Custom Search

Friday, June 15, 2012

Assignment No. 04 Semester: Spring 2012 CS504: Software Engineering-I


Assignment No. 04
Semester: Spring 2012
CS504: Software Engineering-I


Total Marks: 20
Due Date: 18/06/2012

Instructions
Please read the following instructions carefully before assignment submission.

It should be clear that your assignment will not get any credit if:

§  The assignment is submitted after due date.
§  The submitted assignment does not open or file is corrupt.
§  All types of plagiarism are strictly prohibited.


Objective
The objective of this assignment is:

§  To assess your overall understanding of Software Engineering concepts
§  To check your level of understanding for Software Architecture
§  How we create deployment view of system based on scenario description

Note:

The assignment should be in .doc format. Assignment in any format other than MS Word format will not be accepted.




You are required to recall the concepts related to Unified Modeling Language (UML), Software Architecture and deployment view (Krutchen’s 4+1) before solving this assignment.



Assignment


Description: Consider the Healthcare Sales Management system again, this time you are required to draw a deployment diagram for the scenario given below:

Architecture of health care management system consists of two tiers of servers; application server and database server. We have one application server and two database servers. Both database servers are identical; first acts as a main server, while the second acts as a redundant backup in case the first one fails. Clients can access database server through application server.
For above system, we also have the option of using a proprietary client that accesses the databases directly.

Question:
  1. Given the above scenario, you are now required to draw deployment (physical) view based on Krutchen’s 4+1 architectural model for the above system depicting normal client access scenario as well as proprietary client access scenario.
  2. You are also required to explain your deployment diagram that how data will flow from client to server and then from server to client (request initiation to reply from server). Explanation of deployment diagram should be done in not more than 4 to 5 lines.








No comments:

Post a Comment