100% satisfaction guarantee Immediately available after payment Both online and in PDF No strings attached
logo-home
Previously searched by you
Previously searched by you
logo
Software Engineering CA$19.15   Add to cart
Quickly navigate to
Preview
  2.  
  3. Software Engineering
  4.  
  5. Software Engineering
  6.  
  7. Software Engineering

Exam (elaborations)

Software Engineering
 8 views  0 purchase
  • Course
  • Software Engineering
  • Institution
  • Software Engineering

1. Software Engi- neering Multi-person construction of multi-person software. 2. System Purposeful collection of interrelated components working together to achieve a common goal. 3. Requirements Engineering The process of eliciting: The services that the customer requires from a syst...

[Show more]

Preview 4 out of 37  pages

Document information

  • May 25, 2023
  • 37
  • 2022/2023
  • Exam (elaborations)
  • Questions & answers

Subjects

  • 1 software engi neering multi person construction of multi person software 2 system purposeful collection of interrelated components working together to achieve a common goal 3 requi

Written for

  • Software Engineering
  • Software Engineering
  • Software Engineering
All documents for this subject (225)

Seller

avatar-seller
stanleymwaniki

Reviews received

Content preview

Software Engineering
Study online at
https://quizlet.com/_19hgze
1. Software Engi-
Multi-person construction of multi-person software.
neering

2. System Purposeful collection of interrelated components
working together to achieve a common goal.

3. Requirements The process of eliciting: The services that the
Engineering customer requires from a system. The constraints
under which it operates and is developed.

4. Requirements Descriptions of the system services and
constraints
that are generated during the requirement
engineering process.

5. User Require- Statements in natural language and diagrams of
ments the system services and operational constraints.
Written for customers, so it must use their
language and mental model. Understandable for
users who don't have detailed technical
knowledge. UML is your friend.
6. System
Require- ments A structured document setting out detailed
descriptions of the system's functions, services,
and operational con- straints. Defines what
should be implemented. Must be concise in their
7. Functional Re- technical effects.
quirements
Statements of services the system should
provide. How the system should react to
8. Examples of particular inputs. How the system should
Functional Re- behave in particular situation.
quirements
"A library system that provides a single interface
to a num- ber of databases of articles in different
libraries". "Users can search for and download
this articles for personal study". "Users shall be
able to search either all of the initial set of
9. Non-Functional databases or select a subset from it". "The
Requirements
1/

, Software Engineering
Study online at
https://quizlet.com/_19hgze
system shall
provide
appropriate
viewers for the
users to read
documents in the
document store".

These define
system
properties and
constraints.
Properties:
reliability,
response time,
storage
require-
ments.




2/

, Software Engineering
Study online at
Constraints: security, legal impacts, domain expert
work- flow.
Process Requirements: (e.g.,) a particular
programming language.

10. Example of "The user interface for LIBSYS shall be
Non-Functional implemented as simple HTML without frames or
Requirements Java applets". "The
system shall not disclose any personal information
about customers apart from their name and their
registration identification number"."The system
architecture shall be constructed according to the
WC3 standards".

11. UML Unified Modelling Language: Standard language
for spec- ifying, visualising, constructing, and
documenting all the artefacts of a software
system during the software lifecy- cle.

12. UML Behaviour
Diagram al.
Types Functional.
Structural.
13. Behavioural Dia- Activity
grams Diagram.
State
Diagram.
14. Structural Sequence Diagram.
Dia- grams
Class
15. Functional Diagram.
Dia- grams Object
Diagram.
16. Use Case
Dia- gram Use Case Diagram


Functional.

3/

, Software Engineering
Study online at
relationships between actors (interacting with
Visualise the system) and use cases (functionality).




4/

The benefits of buying summaries with Stuvia:

Guaranteed quality through customer reviews

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

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

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 stanleymwaniki. Stuvia facilitates payment to the seller.

Will I be stuck with a subscription?

No, you only buy these notes for CA$19.15. You're not tied to anything after your purchase.

Can Stuvia be trusted?

4.6 stars on Google & Trustpilot (+1000 reviews)

79835 documents were sold in the last 30 days

Founded in 2010, the go-to place to buy study notes for 14 years now

Start selling
CA$19.15
  • (0)
  Add to cart