AssignmentView more random threads:
- MTH301 Calculus II Assignment No.3 Solution Fall Semester...
- cs304 first may spring semester for mcs 2015 final solution
- CS402 Theory of Automata Assignment No 2 fall 11 November...
- CS408 assignment no 4 fall January 2012
- CS506 assignment no 5 fall 2010 solution 29-01-2011
- CS602 Assignment No. 1 Fall spring october 2011
- MCM301 Communication skills Assignment No.1 Solution Spring...
- MTH301 Calculus II Assignment No.2 Solution Spring Semester...
- MTH401 IDEA solution fall 2010 November, 8th
- Assignment No. 01 Semester: Spring 2012 CS609: System...
In continuation of the previous assignment 1 scenario, in which you drew Use Case diagram, then, in second assignment, you developed its class diagram and object relationship.
Now, in third assignment, you are required to draw a table of multiple views as a software architecture for the same scenario (discussed in assignment #1 and 2) by following Krutchen’s 4+1 Architectural View Model.
To make sure that your developed software architecture deals with Abstraction, composition, style and esthetics as well as requirements from different stake holders.
You are required to populate table with Logical view, the process view, the physical view, the development view, and the use case view with respect to scenario in assignment #1.
For your convenience, same scenario is illustrated as follows:
Suppose you are a domain analyst in a renowned software house ABC. You have been given a task to model requirements for domain understanding for a software project. Scenario is given below; Virtual University campuses all over the Pakistan need to establish “Coffee machine” in their respective places to fulfill cafeteria needs and keep students energetic. The prototype of that Coffee machine should be aesthetically good enough and yet easy to handle for an IT-expert. In a brainstorming session of capturing requirements, there comes major functional requirements like place a coffee order, its preparation, serving and maintenance etc. It’s quite simple at first look but in a more elaborated and refined version, it soon turns out that design should pay attention in more details. So for above said core functionalities, there will possibly some extended and included use cases such as for the preparation of coffee, there requires to add milk and insert coffee. Also, maintenance requires clean up and refill. Similarly, order placement also linked with some requirements.
Sponsored Links
There are currently 1 users browsing this thread. (0 members and 1 guests)