Running head: CASE 10 &11 SUMMARIES
Case 10 &11 Summaries
YourFirstName YourLastName
University title
1
CASE 10 &11 SUMMARIES
2
Chapter 10: human-computer interaction layer design
The activities taking place in company shows that the process of designing a humancomputer interaction layer design is very long and demanding. We further realize that it
requires one accept changes be flexible rather than being rigid. The success of Alec’s attempt
to convince Margaret highlights this.
The realized that it was only Place Order, Browse/Search CDs, and Checkout use cases that
were important in this process. The first step in the interface design process was to develop
the key use scenarios for The Internet Sales System. In this, Alec identified the browsing
shopper and the hurry-up shopper as the two use scenarios and many others. He however
ignored the remaining use scenarios beyond the two because they were irrelevant. The next
step was to create a window navigation diagram (WND) in which he began with the Place
Order, Browse/Search CDs, and Checkout essential use cases.
It may be necessary to modify the original essential use cases in light of these new subtypes
of customer. Furthermore, the structural and behavioral models needed modification.
Remember that it is possible uncover object-oriented systems analysis and design which are
incremental and iterative. The system will start with a home Page containing the main menu
for the sales system. Alec identified four operations to support the main menu.
We realize that he succeeded and thus we appreciate Alec’s attempt to convince Margaret
since he did a wonderful thing thereafter. I would advise my team to exactly what Alec did to
successfully come up with a human-computer interaction layer design.
Chapter 11: Physical Architecture Layer Design
Alec applied the same approached he used to install human-computer interaction layer design
.when he and his team were installing CD Selections case. He has spun off part of his team to
focus on designing the physical architecture layer, which was of main concern. However, this
group realized that it had to remain in touch with the other groups due some similarities. By
CASE 10 &11 SUMMARIES
3
considering this, deploying the problem Domain, human–computer interaction and data
management layers over the architecture could not prove to be difficult as such.
Alec as well liked this ensured a coordination efforts exist among the different layer groups
by heading up the physical architecture Layer’s group to understand the implications of
deploying The system over multiple, and possibly incompatible, platforms better.
The new application required hardware, software and networks to support it. The integration
of the three into the current infrastructure then follows.
They came up with a final decision to build server architecture the point at which everyone
believed to be very hard to know how much it trafficked. Website would however perform
that duty. The team made up their mind that the server architecture was the best configuration
for the Internet portion of the server software of Internet sales system and the application
software to run the system. Customers would use their personal computers running a Web
browser. This would be their client. A database server would store the Internet system’s
databases unlike an application server.
The team later created a network model to show the major components of the Internet Sales
system and a deployment diagram that shows how the problem domain, human computer
interaction, and data management Layers would be deployed over the physical architecture
layer. The team finally developed hardware and software specification and handed to the
purchasing department. The process of installing software and hardware requires some
dedication.
CASE 10 &11 SUMMARIES
4