Question 1
Software specification, where customers and engineers define the software
that is to be produced and the constraints on its operation.
Software development, where the software is designed and programmed.
Software validation, where the software is checked to ensure that it is what
the customer requires.
Software evolution, where the software is modified to reflect changing
customer and market requirements.
Question 2
1. Initial The goals associated with the process area are satisfied, and for all
processes the scope of the work to be performed is explicitly set out and
communicated to the team members.
2. Managed At this level, the goals associated with the process area are met, and
organizational policies are in place that define when each process should be used.
There must be documented project plans that define the project goals. Resource
management and process monitoring procedures must be in place across the
institution.
3. Defined This level focuses on organizational standardization and deployment of
processes. Each project has a managed process that is adapted to the project
requirements from a defined set of organizational processes. Process assets and
process measurements must be collected and used for future process
improvements.
4.Quantitatively managed At this level, there is an organizational responsibility to use
statistical and other quantitative methods to control subprocesses. That is, collected
process and product measurements must be used in process management.
5. Optimizing At this highest level, the organization must use the process and
product measurements to drive process improvement. Trends must be analyzed and
the processes adapted to changing business needs.
Question 3
,it is practically impossible to derive a complete set of stable software requirements.
Requirements change because customers find it impossible to predict how a system
will affect working practices, how it will interact with other systems, and what user
operations should be automated. It may only be after a system has been delivered
and users gain experience with it that the real requirements become clear. Even
then, external factors drive requirements change.
Question 4
1. Stakeholders often don’t know what they want from a computer system except
in the most general terms; they may find it difficult to articulate what they want
the system to do; they may make unrealistic demands because they don’t
know what is and isn’t feasible.
2. Stakeholders in a system naturally express requirements in their own terms
and with implicit knowledge of their own work. Requirements engineers,
without experience in the customer’s domain, may not understand these
requirements.
3. Different stakeholders, with diverse requirements, may express their
requirements in different ways. Requirements engineers have to discover all
potential sources of requirements and discover commonalities and conflict.
4. Political factors may influence the requirements of a system. Managers may
demand specific system requirements because these will allow them to
increase their influence in the organization.
5. The economic and business environment in which the analysis takes place is
dynamic. It inevitably changes during the analysis process. The importance of
particular requirements may change. New requirements may emerge from
new stakeholders who were not originally consulted.
Question 5
, Question 6
6.1
A logical view, which shows the key abstractions in the system as objects or
object classes.
A process view, which shows how, at run-time, the system is composed of
interacting processes.
A development view, which shows how the software is decomposed for
development.
A physical view, which shows the system hardware and how software
components are distributed across the processors in the system.
6.2
1. A set of servers that offer services to other components. Examples of servers
include print servers that offer printing services, file servers that offer file
management services, and a compile server that offers programming language
compilation services. Servers are software components, and several servers may
run on the same computer.
2. A set of clients that call on the services offered by servers. There will normally be
several instances of a client program executing concurrently on different computers.
3. A network that allows the clients to access these services. Client–server systems
are usually implemented as distributed systems, connected using Internet protocols
Question 7
7.1
The benefits of buying summaries with Stuvia:
Guaranteed quality through customer reviews
Stuvia customers have reviewed more than 700,000 summaries. This how you know that you are buying the best documents.
Quick and easy check-out
You can quickly pay through credit card or Stuvia-credit for the summaries. There is no membership needed.
Focus on what matters
Your fellow students write the study notes themselves, which is why the documents are always reliable and up-to-date. This ensures you quickly get to the core!
Frequently asked questions
What do I get when I buy this document?
You get a PDF, available immediately after your purchase. The purchased document is accessible anytime, anywhere and indefinitely through your profile.
Satisfaction guarantee: how does it work?
Our satisfaction guarantee ensures that you always find a study document that suits you well. You fill out a form, and our customer service team takes care of the rest.
Who am I buying these notes from?
Stuvia is a marketplace, so you are not buying this document from us, but from seller LOVELY01. Stuvia facilitates payment to the seller.
Will I be stuck with a subscription?
No, you only buy these notes for $2.67. You're not tied to anything after your purchase.