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
Ask a Question
AI Study Help
New
Search
Search
Sign In
Register
study help
business
software testing and quality assurance
Questions and Answers of
Software Testing And Quality Assurance
In what sense does the abstract-data-type architectural style constrain the designer?
Describe in your own words the essence of the implicit-invocation architectural style.
Explain the difference between module, component and connector, and allocation viewpoints.
What is the difference between the conceptual or logical viewpoint and the implementation viewpoint?
What is the difference between the notions software architecture and design pattern?
What is the role of the backlog in design?
Explain the architecture design method ADD (Attribute Driven Design).
What is the relation between design decisions and software architecture?
What is the main purpose of a software architecture?
What is the difference between software architecture and top-level design?
Give a definition of the term ‘software architecture’. Explain the different elements in this definition.
To understand the role and purpose of software architecture assessments
To be able to characterize some important software architectural styles
To be able to document a software architecture in different views
To understand the relation between software architecture and design decisions
To appreciate the role of software architecture in software development
~ In what sense can the interface to a class be considered a contract? What are the repercussions of this for subtyping relations? (See (Meyer, 1992)).
In what respects does a UML state diagram differ from a state transition diagram?
What are CRC cards and use-case scenarios used for in object-oriented analysis and design?
Explain the difference between a class diagram and a component diagram.
Explain the difference between a sequence diagram and a communication diagram.
Explain the difference between a class diagram and a state machine diagram.
Explain the difference between the specialization--generalization relation and the whole--part relation.
Define the following terms: object, state, attribute, message, and inheritance.
Explain the following concepts from entity--relationship modeling: entity, entity type, attribute value, attribute, relationship.
To know the terminology of object orientation
To know about UML, the Unified Modeling Language, and its main diagram types
To know about various classic modeling techniques
~ What are the major uses of a requirements specification. In what ways do these different uses affect the style and contents of a requirements document?
Write a requirements specification for a hypertext browsing system.
~ As an analyst involved in the development of this hypertext browsing system, discuss possible stands in the subjectivist--objectivist and order--conflict dimensions. What are the arguments for and
How would you go about determining the requirements for a hypertext-like browsing system for a technical library. Both users and staff of the library only have experience with keyword-based
~ How would you test the requirements stated in the document from the previous exercise? Are the requirements testable to start with?
Take the requirements specification document from a project you have been involved in and assess it with respect to the requirements for such a document as listed in section 9.2 (unambiguity,
~ Which of the descriptive means mentioned in the previous exercise would you favor for describing the requirements of an office automation system?And which one for an elevator control system?
~ Discuss pros and cons of the following descriptive means for a requirements specification: full natural language, constrained natural language, a pictorial language like UML.
~ Refine the framework in figure 9.1 such that it reflects the situation in which we have to explicitly model both the current and the new work situation.
~ For an office information system, identify different types of stakeholders.Can you think of ways in which the requirements of these stakeholders might conflict?
~ What are major differences in the external environment of an office automation system and that of an embedded system, like an elevator control system. What impact will these differences have on the
Draw up a requirements specification for a system whose development you have been involved with, following IEEE 830.Discuss the major differences between the original specification and the one you
List and discuss major drawbacks of using natural language for specifying requirements.
List and discuss the major quality requirements for a requirements document.
Why is requirements traceability important?
How does the presence of COTS components affect requirements engineering?
Why is the distinction between ‘Attractive’, ‘Must-be’ and ‘One-dimensional’categories of requirements in Kano’s model relevant?
What does MoSCoW stand for?
How can conflicting requirements be represented in viewpoints?
What is goal-oriented requirements engineering?
In which circumstances is ethnography a viable requirements elicitation technique?
Describe the requirements elicitation technique called scenario-based analysis.
Describe the requirements elicitation technique called task analysis.
In what sense are most requirements engineering techniques Taylorian in nature?
What is the difference between an implicit and an explicit conceptual model?
What is requirements elicitation?
What are the four major types of activity in requirements engineering?
To know different ways to structure a set of requirements
To know various techniques and notations for specifying requirements
To be aware of the contents of a requirements specification document
To be able to distinguish a number of requirements elicitation techniques
To appreciate the role of social and cognitive issues in requirements engineering
To understand that requirements engineering is a cyclical process involving four types of activity: elicitation, specification, validation, and negotiation
~ Suppose you are the manager of a project that is getting seriously behind schedule. Your team is having severe problems with testing a particular subsystem. Your client is pressing you to deliver
~ Why is planning (i.e., the activity) more important than the plan (the document)?
~ Suppose one of your team members is dissatisfied with his situation. He has been involved in similar projects for several years now. You have assigned him these jobs because he was performing so
Consider a project you have been involved in. Identify the major irregular, control, and goal variables for this project. In what ways did the control variables influence project control?
~ Discuss the pros and cons of a hierarchical as well as a matrix team organization for the patient planning project.
~ Consider the patient planning system mentioned in exercise 3.12. Suppose the project team consists of several analysts and two members from the hospital staff. The analysts have a lot of experience
Classify a project you have been involved in with respect to product certainty, process certainty, and resource certainty. Which of the archetypal situations sketched in section 8.2 best fits this
What is a PERT chart?
What is a work breakdown structure?
Rephrase the cost drivers of the COCOMO cost estimation model as risk factors.
How can risks be mitigated?
Is the waterfall approach suitable for an exploration-type problem? If so, why?
Is the waterfall approach suitable for a realization-type problem? If so, why?
List the conditions for effective systems control.
To know techniques for the day-to-day planning and control of software development projects
To understand how risks can be prevented from becoming problems
To be aware of typical project situations, and ways in which projects can be successfully dealt with in such situations
To appreciate looking at project control from a system point of view
~ Can you give an intuitive rationale for the values of the COCOMO 2 cost drivers (figure 7.11) that relate to project attributes?
~ Suppose you have a LOC-based cost estimation model available whose parameters are based on projects from your own organization that used COBOL as the implementation language. Can you use this model
~ Suppose you are managing a project which is getting behind schedule.Possible actions include: renegotiating the time schedule, adding people to the project, and renegotiating quality requirements.
How would you calibrate the COCOMO 2 model to fit software development in your organization?
Why should software cost models be recalibrated from time to time?
Suppose you are involved in a project which is estimated to take 100 manmonths. How would you estimate the nominal calendar time required for this project? Suppose the project is to be finished
Why is it difficult to compare different cost estimation models?
How may early cost estimates influence the way in which a project is executed?
In which sense does Function Point Analysis (FPA) reflect the batch-oriented world of the 1970s?
Give a rationale for Brooks’ Law.
Discuss the major differences between COCOMO 2 and FPA.
Give a sketch of COCOMO 2.
Give a sketch of Function Point Analysis (FPA).
How may the Rayleigh-curve be related to software cost estimation?
What does the Walston--Felix model look like?
In which ways may political arguments influence cost estimates?
To understand techniques for relating effort to development time
To understand well-known techniques for estimating software cost and effort
To have insight in the factors that affect software development productivity
To appreciate the use of quantitative, objective approaches to software cost estimation
~ In 1988 and 1998, two surveys were conducted to assess the state of the art in software cost estimation in the Netherlands. One of the questions concerned the various stakeholders involved in
Showing 2400 - 2500
of 3313
First
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
Last