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

Result Not Found

Books FREE
Tutors
Study Help
Hire a Tutor
AI Tutor New

Search
Sign In
Register

study help
computer science
introduction to software engineering

Questions and Answers of Introduction To Software Engineering

10.2. Why are control components necessary in traditional software and generally not required in object-oriented software?
Do the rules of interaction help a knowledgeable user to work efficiently?
Is the system usable without continual help or instruction?
10.14. Why is “chunking” important during the component-level design review process?
10.13. Select a small coded component and represent it using (1) an activity diagram, (2) a flowchart, (3) a decision table, and (4) PDL.
10.12. All modern programming languages implement the structured programming constructs. Provide examples from three programming languages.
10.11. Select a small portion of an existing program (approximately 50 to 75 source lines).Isolate the structured programming constructs by drawing boxes around them in the source code. Does the
10.10. What is a WebApp component?
10.9. Are stepwise refinement and refactoring the same thing? If not, how do they differ?
10.8. Develop (1) an elaborated design class, (2) interface descriptions, (3) an activity diagram for one of the operations within the class, and (4) a detailed statechart diagram for one of the
10.7. Is it reasonable to say that problem domain components should never exhibit external coupling? If you agree, what types of component would exhibit external coupling?
10.6. Select three components that you have developed recently and assess the types of coupling that each exhibits. If you had to define the primary benefit of low coupling, what would it be?
10.5. Select three components that you have developed recently and assess the types of cohesion that each exhibits. If you had to define the primary benefit of high cohesion, what would it be?
10.4. Describe the DIP in your own words. What might happen if a designer depends too heavily on concretions?
010.3. Describe the OCP in your own words. Why is it important to create abstractions that serve as an interface between components?
9.7. If you haven’t done so, complete Problem 6.6. Use the design methods described in this chapter to develop a software architecture for the PHTRS.
9.6. Research the ATAM (using [Kaz98]) and present a detailed discussion of the six steps presented in Section 9.5.1.
9.5. Select an application with which you are familiar. Answer each of the questions posed for control and data in Section 9.3.3.
8.6. Describe software architecture in your own words.
8.5. Provide examples of three data abstractions and the procedural abstractions that can be used to manipulate them.
8.4. Examine the task set presented for design. Where is quality assessed within the task set?How is this accomplished? How are the quality attributes discussed in Section 8.2.1 achieved?
8.3. How do we assess the quality of a software design?
8.2. If a software design is not a program (and it isn’t), then what is it?
8.1. Do you design software when you “write” a program? What makes software design different from coding?
What uniform criteria define the technical quality of a software design?
How is function or data structure detail separated from a conceptual representation of the software?
What criteria can be used to partition software into individual components?
8. Develop a deployment model.
7. Conduct component-level design.Specify all algorithms at a relatively low level of abstraction.Refine the interface of each component.Define component-level data structures.Review each component
6. Design the user interface:Review results of task analysis.Specify action sequence based on user scenarios.Create behavioral model of the interface.Define interface objects, control
5. Design any interface required with external systems or devices.
8.8. Describe separation of concerns in your own words. Is there a case when a divide-andconquer strategy may not be appropriate? How might such a case affect the argument for modularity?
9.4. The terms architectural style, architectural pattern, and framework (not discussed in this book) are often encountered in discussions of software architecture. Do some research and describe how
9.3. Some of the architectural styles noted in Section 9.3.1 are hierarchical in nature and others are not. Make a list of each type. How would the architectural styles that are not hierarchical be
9.2. Present two or three examples of applications for each of the architectural styles noted in Section 9.3.1.
9.1. Using the architecture of a house or building as a metaphor, draw comparisons with software architecture. How are the disciplines of classical architecture and the software architecture similar?
Alarm processing—verifies and acts on all alarm conditions?
Detector management—coordinates access to all detectors attached to the system.
Control panel processing—manages all control panel functionality.
External communication management—coordinates communication of the security function with external entities such as other Internet-based systems and external alarm notification.
8.15. Briefly describe each of the four elements of the design model.
8.14. Does “refactoring” mean that you modify the entire design iteratively? If not, what does it mean?
8.13. Consider the software required to implement a full navigation capability (using GPS) in a mobile, handheld communication device. Describe two or three crosscutting concerns that would be
8.12. Apply a “stepwise refinement approach” to develop three different levels of procedural abstractions for one or more of the following programs: (a) Develop a check writer that, given a
8.11. How are the concepts of coupling and software portability related? Provide examples to support your discussion.
8.10. Discuss the relationship between the concept of information hiding as an attribute of effective modularity and the concept of module independence.
4. Create a set of design classes or components:Translate analysis class description into a design class.Check each design class against design criteria;consider inheritance issues.Define methods and
Has the system been tuned to the physical and social environment in which it will be used?
3. Create a sequence for each use case.
Should navigation be accomplished via links, via search-based access, or by some other means?
Should certain elements be presented to users based on the context of previous navigation actions?
Should a navigation log be maintained for users?
Should a full navigation map or menu (as opposed to a single “back” link or directed pointer) be available at every point in a user’s interaction?
Should navigation design be driven by the most commonly expected user behaviors or by the perceived importance of the defined WebApp elements?
Can a user “store” his previous navigation through the WebApp to expedite future usage?
For which user category should optimal navigation be designed?
How should links external to the WebApp be handled? Overlaying the existing browser window? As a new browser window? As a separate frame?
7.1. What is the fundamental difference between the structured analysis and object-oriented strategies for requirements analysis?
7.2. In a data flow diagram, does an arrow represent a flow of control or something else?
7.3. What is “information flow continuity” and how is it applied as a data flow diagram is refined?
7.4. How is a grammatical parse used in the creation of a DFD?
7.5. What is a control specification?
7.6. Are a PSPEC and a use case the same thing? If not, explain the differences.
Should navigation to related groups of elements be given priority over navigation to a specific element?
How should navigation errors be handled?
4. Build a state diagram for the system.
5. Review the behavioral model to verify accuracy and consistency.
Each passive sensor must have some method to read sensor input and attributes that represent the sensor value.
Each active sensor must have capabilities to broadcast update messages when its value changes.
Each active sensor should send a life tick, a status message issued within a specified time frame, to detect malfunctions.
Each actuator must have some method to invoke the appropriate response determined by the ComputingComponent.
Each sensor and actuator should have a function implemented to check its own operation state.
Each sensor and actuator should be able to test the validity of the values received or sent and set its operation state if the values are outside of the specifications.
Q1: What output video resolution is provided by SafeHome cameras?
Q2: What occurs if an alarm condition is encountered while the camera is being monitored?
Q3: How does the system handle cameras that can be panned and zoomed?
Q4: What information should be provided along with the camera view? (For example, location? time/date? last previous access?)
Should certain elements be easier to reach (require fewer navigation steps)than others? What is the priority for presentation?
Should certain elements be emphasized to force users to navigate in their direction?
7.8. How does a sequence diagram differ from a state diagram. How are they similar?
7.9. Suggest three requirements patterns for a modern mobile phone and write a brief description of each. Could these patterns be used for other devices. Provide an example.
7.11. How much analysis modeling do you think would be required for SafeHomeAssured.com? Would each of the model types described in Section 7.5.3 be required?
2. Using the analysis model, select an architectural style that is appropriate for the software.
Do users work normal office hours or do they work until the job is done?
How are users compensated for the work they perform?
Will the users be represented predominately by one gender?
What is the age range of the user community?
Are users expert typists or keyboard phobic?
Are the users capable of learning from written materials or have they expressed a desire for classroom training?
What level of formal education does the average user have?
Are users trained professionals, technicians, clerical, or manufacturing workers?
Is the interaction simple?
Is the interface tolerant of errors that are made?
Does the interaction anticipate errors and help the user correct them?
Are interaction mechanisms, icons, and procedures consistent across the interface?
Is the interface structured in a logical and consistent manner?
1. Examine the information domain model, and design appropriate data structures for data objects and their attributes.
8. A design should be represented using a notation that effectively communicates its meaning.
7.12. What is the purpose of the interaction model for a WebApp?
7.14. What is the purpose of a configuration model?

Showing 1000 - 1100 of 1534

First
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16

Services

Sitemap
Fun
Definitions
Become Tutor
Study Help Categories
Recent Questions
Expert Questions

Company Info

Security
Copyrights
Privacy Policy
Terms & Conditions
SolutionInn Fee
Scholarship

Get In Touch

About Us
Contact Us
Career
Jobs
FAQ
Campus Ambassador

Secure Payment

Download Our App

© 2024 SolutionInn. All Rights Reserved