All Matches
Solution Library
Expert Answer
Textbooks
Search Textbook questions, tutors and Books
Oops, something went wrong!
Change your search query and then try again
Toggle navigation
FREE Trial
S
Books
FREE
Tutors
Study Help
Expert Questions
Accounting
General Management
Mathematics
Finance
Organizational Behaviour
Law
Physics
Operating System
Management Leadership
Sociology
Programming
Marketing
Database
Computer Network
Economics
Textbooks Solutions
Accounting
Managerial Accounting
Management Leadership
Cost Accounting
Statistics
Business Law
Corporate Finance
Finance
Economics
Auditing
Hire a Tutor
AI Tutor
New
Search
Search
Sign In
Register
study help
computer science
introduction to software engineering
Questions and Answers of
Introduction To Software Engineering
13.7. What is the difference between content architecture and WebApp architecture?
13.6. Consider the content object Order, generated once a user of SafeHomeAssured.com has completed the selection of all components and is ready to finalize his purchase. Develop a UML description
13.5. What is the most aesthetically pleasing website you have ever visited and why?
13.4. You are a WebApp designer for FutureLearning Corporation, a distance learning company.You intend to implement an Internet-based “learning engine” that will enable you to deliver course
13.3. Add at least five additional questions to the WebApp Design—Quality Checklist presented in Section 13.1.
13.2. In this chapter we select a broad array of quality attributes for WebApps. Select the three that you believe are most important, and make an argument that explains why each should be emphasized
13.1. Why is the “artistic ideal” an insufficient design philosophy when modern WebApps are built? Is there ever a case in which the artistic ideal is the philosophy to follow?
Is content well organized? Indexed? Easily accessible?
Is content valuable to the targeted user community?
Is content unique? That is, does the WebApp provide some unique benefit to those who use it?
Is content credible?
Are the content and its location stable (i.e., will they remain at the referenced URL)?
Is it possible to determine the currency of the content, the last update, and what was updated?
Can the background and authority of the content’s authors be easily identified?
Can the scope and depth of content be easily determined to ensure that it meets the user’s needs?
Have graphics and other nontext media been used appropriately? Are graphics file sizes optimized for display efficiency?
Can content and/or functionality be customized to the bandwidth at which the user communicates?
Can content and/or function and/or navigation options be tailored to the user’s preferences?
Is the WebApp instrumented with site management utilities that include tools for usage tracking, link testing, local searching, and security?
Is it likely that most links have persistence on the Web?
Do all pointers provide links to information that is of interest to users?
Is the overall page design easy to read and navigate?
Is HTML optimized to eliminate inefficiencies?
Are tables organized and sized in a manner that makes them understandable and displayed efficiently?
12.14. Find three patterns repositories for WebApp patterns. Select one pattern from each and present an abbreviated description of it.
12.13. Find three patterns repositories for user interface patterns. Select one pattern from each and present an abbreviated description of it.
12.12. The gang of four [Gam95] have proposed a variety of component patterns that are applicable to object-oriented systems. Select one (these are available on the Web) and discuss it.
12.11. Using the design pattern template presented in Section 12.1.3, develop a complete pattern description for the Kitchen pattern mentioned in Section 12.3.
12.10. Build a pattern-organizing table for the patterns you used in Problem 12.9.
12.9. Using the pattern-based design tasks noted in Section 12.2.3, develop a skeletal design for the “interior design system” described in Section 11.3.2.
12.8. When Christopher Alexander says “good design cannot be achieved simply by adding together performing parts,” what do you think he means?
12.7. Find five patterns repositories and present an abbreviated description of the types of patterns contained in each.
12.6. Develop a skeletal pattern language for a sport with which you are familiar. You can begin by addressing the context, the system of forces, and the broad problems that a coach and team must
12.5. Using the design pattern template presented in Section 12.1.3, develop a complete pattern description for a pattern suggested by your instructor.
12.4. What is a framework and how does it differ from a pattern? What is an idiom and how does it differ from a pattern?
12.3. How do architectural patterns differ from component patterns?
12.2. What is the difference between a nongenerative and a generative pattern?
12.1. Discuss the three “parts” of a design pattern and provide a concrete example of each from some field other than software.
How to establish Internet-based monitoring and control of an installed security system?
How to sell SafeHome products and services to customers
How to provide information about SafeHome products and services
6. Refine the design by adapting each pattern to the specifics of the software you’re trying to build.
5. Repeat steps 1 to 4 until the complete design is fleshed out.
4. “Work inward from the context” [Sha05] looking for patterns at lower levels of abstraction that contribute to the design solution.
3. Begin your design with “big picture” patterns that establish a context or skeleton for further design work.
2. Examining the big picture, extract the patterns that are present at that level of abstraction.
1. Be sure you understand the big picture—the context in which the software to be built resides. The requirements model should communicate this to you.
3. Design patterns are less specialized than frameworks. Frameworks always have a particular application domain. In contrast, design patterns can be used in nearly any kind of application. While more
2. Design patterns are smaller architectural elements than frameworks. A typical framework contains several design patterns but the reverse is never true.
1. Design patterns are more abstract than frameworks. Frameworks can be embodied in code, but only examples of patterns can be embodied in code. A strength of frameworks is that they can be written
If a large report is to be presented, how should it be partitioned for ease of understanding?
Is proper on-screen identification assigned to all content?
Will mechanisms be available for moving directly to summary information for large collections of data?
Will graphical output be scaled to fit within the bounds of the display device that is used?
How will color be used to enhance understanding?
How will error messages and warnings be presented to the user?
1. Using information developed during interface analysis (Section 11.3), define interface objects and actions (operations).
1. Evaluate all use cases to fully understand the sequence of interaction within the system.
List all sensors that are “read” by the software.
List all interrupt conditions.
List all “switches” that are actuated by an operator.
List all data conditions.
Recalling the noun/verb parse that was applied to the processing narrative, review all “control items” as possible control specification inputs/outputs.
Focus on possible omissions—a very common error in specifying control; for example, ask: “Is there any other way I can get to this state or exit from it?”
Describe the behavior of a system by identifying its states, identify how each state is reached, and define the transitions between states.
What work will the user perform in specific circumstances?
Can the user customize the screen location for content?
7.7. There are two different types of “states” that behavioral models can represent. What are they?
2. Define events (user actions) that will cause the state of the user interface to change. Model this behavior.
7.10. Select one of the patterns you developed in Problem 7.9 and develop a reasonably complete pattern description similar in content and style to the one presented in Section 7.4.2.
What is the primary spoken language among users?
What are the consequences if a user makes a mistake using the system?
Are users experts in the subject matter that is addressed by the system?
Do users want to know about the technology that sits behind the interface?
Is the software to be an integral part of the work users do or will it be used only occasionally?
What tasks and subtasks will be performed as the user does the work?
What specific problem domain objects will the user manipulate as work is performed?
What is the sequence of work tasks—the workflow?
What is the hierarchy of tasks?
1. Each user implements different tasks via the interface; therefore, the look and feel of the interface designed for the patient will be different than the one defined for pharmacists or physicians.
2. The interface design for pharmacists and physicians must accommodate access to and display of information from secondary information sources(e.g., access to inventory for the pharmacist and access
3. Many of the activities noted in the swimlane diagram can be further elaborated using task analysis and/or object elaboration (e.g., Fills prescription could imply a mail-order delivery, a visit to
7.13. It could be argued that a WebApp functional model should be delayed until design.Present pros and cons for this argument.
2. Identify events that drive the interaction sequence and understand how these events relate to specific objects.
Do interaction mechanisms become more flexible as users become more knowledgeable?
Exception handling.
Embedded design assumptions, including the use of specific numerical or nonnumerical algorithms.
3. Partition the analysis model into design subsystems and allocate these subsystems within the architecture:Be certain that each subsystem is functionally cohesive.Design subsystem
Security features, including access controls and authentication protocol.
Service requirements, including operating system interfaces and support from other components.
Run-time requirements, including resource usage (e.g., memory or storage), timing or speed, and network protocol.
Development and integration tools required by the component.
Application programming interface (API).
5. Develop a requirements model for the classes.
4. Analyze each application in the sample and define analysis classes.
3. Collect a representative sample of applications in the domain.
2. Categorize the items extracted from the domain.
1. Define the domain to be investigated.
9.8. Using a data flow diagram and a processing narrative, describe a computer-based system that has distinct transform flow characteristics. Define flow boundaries and map the DFD into a software
10.1. The term component is sometimes a difficult one to define. First provide a generic definition, and then provide more explicit definitions for object-oriented and traditional software.Finally,
Showing 900 - 1000
of 1534
First
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16