New Semester
Started
Get
50% OFF
Study Help!
--h --m --s
Claim Now
Question Answers
Textbooks
Find textbooks, questions and answers
Oops, something went wrong!
Change your search query and then try again
S
Books
FREE
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
Tutors
Online Tutors
Find a Tutor
Hire a Tutor
Become a Tutor
AI Tutor
AI Study Planner
NEW
Sell Books
Search
Search
Sign In
Register
study help
computer science
introduction to software engineering
Software Engineering A Practitioner's Approach 7th Edition Roger Pressman - Solutions
13. Is the system designed for multiple installations in different organizations?
14. Is the application designed to facilitate change and ease of use by the user?
Does the user interface promote usability?
Are the aesthetics of the WebApp appropriate for the application domain and pleasing to the user?
Is the content designed in a manner that imparts the most information with the least effort?
Is navigation efficient and straightforward?
Has the WebApp architecture been designed to accommodate the special goals and objectives of WebApp users, the structure of content and functionality, and the flow of navigation required to use the system effectively?
Are components designed in a manner that reduces procedural complexity and enhances correctness, reliability, and performance?
23.1. Measurement theory is an advanced topic that has a strong bearing on software metrics.Using [Zus97], [Fen91], [Zus90], or Web-based sources, write a brief paper that outlines the main tenets of measurement theory. Individual project: Develop a presentation on the subject and present it to
How does a software project manager select a set of software engineering work tasks?
How is a project schedule created?
2. Meet with stakeholders to address clarification issues.
3. Jointly develop a statement of scope.
4. Review the statement of scope with all concerned.
5. Modify the statement of scope as required.
1. Review the customer request.
2. Plan and schedule a formal, facilitated meeting with all stakeholders.
3. Conduct research to specify the proposed solution and existing approaches.
4. Prepare a “working document” and an agenda for the formal meeting.
5. Conduct the meeting.
6. Jointly develop mini-specs that reflect data, functional, and behavioral features of the software. Alternatively, develop use cases that describe the software from the user’s point of view.
1. Develop list of clarification issues.
Mavericks may have to be excluded from the team, if team cohesiveness is to be maintained.
Why are maintenance and reengineering so important for both software engineering managers and practitioners?1. Senior managers who define the business issues that often have a significant influence on the project.2. Project (technical) managers who must plan, motivate, organize, and control the
Difficulty of the problem to be solved
“Size” of the resultant program(s) in lines of code or function points
Time that the team will stay together (team lifetime)
Degree to which the problem can be modularized
Required quality and reliability of the system to be built
Rigidity of the delivery date
Degree of sociability (communication) required for the project?1. A closed paradigm structures a team along a traditional hierarchy of authority.Such teams can work well when producing software that is quite similar to past efforts, but they will be less likely to be innovative when working within
Team members must have trust in one another.
The distribution of skills must be appropriate to the problem.
7. Review each mini-spec or use case for correctness, consistency, and lack of ambiguity.
10. Is the internal processing complex?
Formulation. The derivation of software measures and metrics appropriate for the representation of the software that is being considered.
1. Has the change specified in the ECO been made? Have any additional modifications been incorporated?
2. Has a technical review been conducted to assess technical correctness?
3. Has the software process been followed and have software engineering standards been properly applied?
4. Has the change been “highlighted” in the SCI? Have the change date and change author been specified? Do the attributes of the configuration object reflect the change?
5. Have SCM procedures for noting the change, recording it, and reporting it been followed?
6. Have all related SCIs been properly updated?
Who assumes responsibility for the accuracy of the information on the website?
Who ensures that quality control processes have been followed before information is published to the site?
Who is responsible for making changes?
Who assumes the cost of change?
What mechanism is used to apprise others of changes that are made?
How can we ensure that changes have been made properly?
21.12. Using one or more of the information sources noted in the references to this chapter or Further Readings and Information Sources, develop a half-hour presentation on the basic syntax and semantics of a formal specification language other than OCL or Z.
How do I ensure that I’ve done it right?
New business or market conditions dictate changes in product requirements or business rules.
New stakeholder needs demand modification of data produced by information systems, functionality delivered by products, or services delivered by a computer-based system.
Reorganization or business growth/downsizing causes changes in project priorities or software engineering team structure.
Budgetary or scheduling constraints cause a redefinition of the system or product.
How does a software team identify the discrete elements of a software configuration?
How does an organization manage the many existing versions of a program(and its documentation) in a manner that will enable change to be accommodated efficiently?
How does an organization control changes before and after software is released to a customer?
Who has responsibility for approving and ranking requested changes?
22.1. Why is the First Law of System Engineering true? Provide specific examples for each of the four fundamental reasons for change.
22.2. What are the four elements that exist when an effective SCM system is implemented?Discuss each briefly.
Interpretation. The evaluation of metrics resulting in insight into the quality of the representation.
Feedback. Recommendations derived from the interpretation of product metrics transmitted to the software team.
1. Does the system require reliable backup and recovery?
2. Are specialized data communications required to transfer information to or from the application?
3. Are there distributed processing functions?
4. Is performance critical?
5. Will the system run in an existing, heavily utilized operational environment?
6. Does the system require online data entry?
7. Does the online data entry require the input transaction to be built over multiple screens or operations?
8. Are the ILFs updated online?
Analysis. The computation of metrics and the application of mathematical tools.
Collection. The mechanism used to accumulate data required to derive the formulated metrics.
22.3. Discuss the reasons for baselines in your own words.
22.4. Assume that you’re the manager of a small project. What baselines would you define for the project and how would you control them?
22.5. Design a project database (repository) system that would enable a software engineer to store, cross reference, trace, update, and change all important software configuration items.How would the database handle different versions of the same program? Would source code be handled differently
22.6. Research an existing SCM tool and describe how it implements control for versions, variants, and configuration objects in general.
22.7. The relations and represent simple relationships between configuration objects. Describe five additional relationships that might be useful in the context of an SCM repository.
22.8. Research an existing SCM tool and describe how it implements the mechanics of version control. Alternatively, read two or three papers on SCM and describe the different data structures and referencing mechanisms that are used for version control.
22.9. Develop a checklist for use during configuration audits.
22.10. What is the difference between an SCM audit and a technical review? Can their function be folded into one review? What are the pros and cons?
22.11. Briefly describe the differences between SCM for conventional software and SCM for WebApps.
22.12. What is content management? Use the Web to research the features of a content management tool and provide a brief summary.
9. Are the inputs, outputs, files, or inquiries complex?
Test proper deletion of an item from the shopping cart.
2. The interface model is reviewed to ensure that all use cases can be accommodated.
1. The content model for the WebApp is reviewed to uncover errors.
5. Some errors are due to the static operating environment (i.e., the specific configuration in which testing is conducted), while others are attributable to the dynamic operating environment (i.e., instantaneous resource loading or time-related errors).
4. Because WebApps reside within a client-server architecture, errors can be difficult to trace across three architectural layers: the client, the server, or the network itself.
3. Although some errors are the result of incorrect design or improper HTML(or other programming language) coding, many errors can be traced to the WebApp configuration.
2. Because a WebApp is implemented in a number of different configurations and within different environments, it may be difficult or impossible to reproduce an error outside the environment in which the error was originally encountered.
1. Because many types of WebApp tests uncover problems that are first evidenced on the client side (i.e., via an interface implemented on a specific browser or a personal communication device), you often see a symptom of the error, not the error itself.
Security is tested by assessing potential vulnerabilities and attempting to exploit each. Any successful penetration attempt is deemed a security failure?
Interoperability is tested to ensure that the WebApp properly interfaces with other applications and/or databases.
Compatibility is tested by executing the WebApp in a variety of different host configurations on both the client and server sides. The intent is to find errors that are specific to a unique host configuration.
Performance is tested under a variety of operating conditions, configurations, and loading to ensure that the system is responsive to user interaction and handles extreme loading without unacceptable operational degradation.
Navigability is tested to ensure that all navigation syntax and semantics are exercised to uncover any navigation errors (e.g., dead links, improper links, erroneous links).
Usability is tested to ensure that each category of user is supported by the interface and can learn and apply all required navigation syntax and semantics.
Structure is assessed to ensure that it properly delivers WebApp content and function, that it is extensible, and that it can be supported as new content or functionality is added.
Function is tested to uncover errors that indicate lack of conformance to customer requirements. Each WebApp function is assessed for correctness, instability, and general conformance to appropriate implementation standards (e.g., Java or AJAX language standards).
3. The design model for the WebApp is reviewed to uncover navigation errors.
Showing 500 - 600
of 1534
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
Last
Step by Step Answers
Get 50% OFF
Claim Now
