Software: computer programs and associated documentation such as requirements, design models and user manuals.

Software engineering: engineering discipline that is concerned with all aspects of software production.
Computer science focuses on theory and fundamentals; software engineering is concerned with the practicalities of developing and delivering
useful software.
Challenges: Coping with increasing diversity, demands for reduced delivery times and developing trustworthy software.
General issues that affect most software :-
Heterogeneity Increasingly, systems are required to operate as distributed systems across networks that include different types of computer
and mobile devices.
Business and social change Business and society are changing incredibly quickly as emerging economies develop and new technologies become
available. They need to be able to change their existing software and to rapidly develop new software.
Security and trust As software is intertwined with all aspects of our lives, it is essential that we can trust that software.
s/ware app types :- Stand-alone applications ,Interactive transaction-based applications, Embedded control systems
Ethical principal: PUBLIC. CLIENT AND EMPLOYER.MANAGEMENT . PROFESSION. COLLEAGUES. SELF

THE PURPOSES OF ANALYSIS AND DESIGN

To transform the requirements into a design of the system to-be
To evolve a robust architecture for the system
To adapt the design to match the implementation environment, designing it for performance

Uml diagram
-use case diagram
-activity diagram

Use case
The purpose of use case diagram is to capture the dynamic aspect of a system which are used to gather the requirements of a system including
internal and external influences. These requirements are mostly design requirements. Hence, when a system is analyzed to gather its
functionalities, use cases are prepared and actors are identified.
Purpose:-
-Used to gather the requirements of a system.
-Used to get an outside view of a system.
-Identify the external and internal factors influencing the system.
-Show the interaction among the requirements are actors.

Activity diagram
Activity diagram is another important diagram in UML to describe the dynamic aspects of the system. Activity diagram is basically a flowchart to
represent the flow from one activity to another activity. The activity can be described as an operation of the system.
Purpose:-
Draw the activity flow of a system.
Describe the sequence from one activity to another.
Describe the parallel, branched and concurrent flow of the system.

CHAP 3
SDLC:-
Specification An explicit set of requirements of a material, design, produc, or service. ; Design- The creation of a plan, idea, model or convention
for conostruction of a system.
Implementation The execution of a plan, idea, model or convention of a system;
Verification The acts of reviewing and inspecting in order to establish and document that a product, service or system meets regulartory or
technical standards; Validation Checking that a software system meets specifications and fulfills its intended purpose;
Evolution Deployment & maintenance
A software process model is an abstract representation of a process. It presents a description of a process from some particular perspective.
Build-and-fix model, Linear/Classical Mode - Waterfall Model, Rapid prototyping model,V Model,Hybrid Model Spiral Model,Evolutionary
Model-Incremental model,Extreme programming (XP),Rational Unified Process (RUP).

Waterfall
Requirements analysis and definition - System and software design - Implementation and unit testing - Integration and system testing - Operation
and maintenance
The main drawback of the waterfall model is the difficulty of accommodating change after the process is underway. One phase has to be
complete before moving onto the next phase so it is not flexible.
Evolutionary Development
Exploratory development - Objective is to work with customers and to evolve a final system from an initial outline specification. Should start
with well-understood requirements and add new features as proposed by the customer.
Throw-away prototyping - Objective is to understand the system requirements. Should start with poorly understood requirements to clarify
what is really Needed.
Adv
1. Assists to identify any problems with the efficacy of earlier design, requirements analysis and coding activities
2. Helps to refine the potential risks associated with the delivery of the system being developed
3. Various aspects can be tested and quicker feedback can be got from the user
4.Helps to deliver the product in quality easily
5.Increases system development speed
Disadv
1.Over long periods, can cause loss in consumer interest and subsequent cancellation due to a lack of a market (for commercial products)
2.May slow the development process, if there are large numbers of end users to satisfy.
3.Not suitable for large applications

Chap 4
-Key activities in PM are project planning, cost and effort estimation, project tracking, project organization, risk management.
-Key tools are Work breakdown structure, product breakdown structure (VPM in software projects), Gantt and Pert charts, process and product
Measures.
Software System (functions and quality)

Calendar time Cost

Ensuring that software is delivered on time, on budget, in accordance with the requirements
Project management is needed because software development is always subject to budget and schedule constraints that are set by the
organisation developing the software.
Factor that affecting PM
1. Team Management
2. Multiple complicated user level requirements

CHAP5

Requirements may be functional or nonfunctional : Functional requirements describe system services or features.
Non-functional requirements is a constraint on the system or on the development process.
Requirements Definition : - A statement in natural language of the services the system provides and its operational constraints
-Written for customers
Requirements Specification :- A structured document setting out detailed descriptions of the system services, Written as a contract between
client and contractor , Written for contractors and developers.

REQUIREMENTS DETERMINATION AND SPECIFICATIONS

Determination is about discovering requirements documenting them in a narrative form.
Discovery takes the name of elicitation: interviews to customers/stakeholders, interviews to domain expert, Questionnaires/survey
Brainstorming, prototyping

REQUIREMENTS DISCOVERY
1. Interviewing 3. Scenerios
2. Use case 4.Ethnography

Requirement writing