Notesale: Turn your study into money

Document Preview

Extracts from the notes are below, to see the PDF you'll receive please use the links above

---

SOFTWARE ENGINEERING
Name of modules:1) Fundamental of S
...

2) System analysis
3) System planning
4) System design
5) System documentation
6) Coding and programming
7) Software testing
8) Cost and time estimation
9) Software project management
10)
Software quality
11)
CASE
...

 Set of program-> software
...
Program is generally used
the developer of a specific program to make a particular software
...

Most of software is custom build rather than assemble from
existing component
...

Easy to modified
...

Software product may be developed for a particular customer or
for the general market
...

program
software
1) Small in size
...

3) Single developer
...

5) Lack proper interface
...


1)
2)
3)
4)
5)
6)

Large in size
...

Team developer
...

Well define interface
...


Definition of software: - it is systematic approach to the
development, operation, maintenance and retirement of software
...
In the current scenario the S
...


Why software engineering:1) In the late 1960’s hardware price were falling but software price
rising
...

3) Large software project required large development loams
...

5) Complicity of software project is increased
...


Why study software engineering?
1)
2)
3)
4)
5)

Higher productivity
...

Ability to solve complex programming problems
...

Better quality programmers
...

Application software
...

Embedded software
...

Web application software
...


The concept analysis in the view of S
...

System development life cycle (SDLC)
...

Object- data base and flow base analysis
...


1) The concept analysis in the view of S
...
E
the analysis phase helps to determine from the starting of the
project to the end of the project
...
We
can make particular software for real time use
...
In the S
...
In a
overview we can say that the software analysis is a main term
through we can developed, operate and maintain a particular
software
...

The software analysis we can determine by the view of two
Side
...

b) For the customer (client)
...
SDLC focus on the internal phase to the end phase for
making particular software
...
SDLC has some specific phase
...
In this phase the analyst set up some
meeting with the corresponding client for making the desired
software
...

a) Technical b) financial c) social feasibility
...
It has some
pen and paper base
...


4) System design: - in this phase the analyst draw the
corresponding diagrams related to the particular software
...

5)

System development: - development refers in the
form of coding, error checking and debarking for the particular
software
...


6)

System testing: - testing refers whatever analyst and

developer done will it be correct and error free to the desired
software
...
E there some testing technique to which we
can check whether project is error free
...
The main testing
techniques are
1) white box testing
2) black box testing
3) ad hope testing
4) system testing
5) unit testing
6) alpha testing
7) beta testing

7) System implementation: - after completing the
testing phase we have to implement a particular product or system
according to the customer need
...

8)

System maintenance: - after implementation the
users use the particular software to there corresponding
operation to active there job
...
In this phase the related
hardware, software and other utilities are also maintained
...
The documentation refers some writing
instruction for how to use for related hardware requirement, and
also some maintains factors for the users
...
After collecting the necessary data from SDLC we have
to summarize the useful and appropriate data for making desired
software
...


Characteristics of SRS1)
2)
3)
4)
5)
6)

complete
traceable
appropriate for the developer
modifiable
simple language
software requirement view

Good SRS: - SRS is a very important for fact gathering
technique which include the consider delimiting with the customer
gather previous information related to particular software and
returned on investment the good characteristics of SRS includes
the following activities:
1) It focuses on summarized from for a particular software
specification
...

3) The traceable factor focus on the modification part when
ever it necessary for the development of SRS
...
These
phases are:
1) Communication (requirement analysis, specification)
...

3) Modeling (analysis, design)
...

5) Deployment (delegacy, support, fid back)
...

b) Iterative waterfall model and the classical waterfall
model are the two types are these model available
calices
...
But in the iterative
model we can jump over from one phase to another
phase
...

2) Intel finished the project the working versa is not
available for the customer
...

4) In this model the risk factor is not available
...

The stages of the model are:
1) planning
2) risk analysis
3) development
4) customer assessment
a) determine objective alternative
b) evaluative alternative risk analysis
c) development and product
d) plane for next phase
From the above figure we can see that there are
four parts including some loops how ever the number of
loops is not fixed depending on the project
...
In this model
the phases are planning, risk analysis, development and
customer assessment
...

The next part deals and evaluated some alternative way
by which we can achieve a simple solution
...


Difference between system analysis and
system designSystem analysis

System design

1) System analysis is the
examination of the problem
...


2) It is concerned with
identifying all constrains
...


3) It deals with data collection
and a datelined evaluation of
existing file
...
It also deals with
program construction testing
and user acceptance
...


4) It provides technical
specification and reports by
which problems can be
trapped
...

program
1)
2)
3)
4)
5)

Small project
...

Cheap
Few sequential changes
...


Module 4
System planning
1) What is system planning?
By the planning in S
...
the planning involves
the software developer and client base future planning from the
starting to the ending phase for making a successful software
...


2) Data and fact gathering
...

For collecting data and fact from the real world
...

This technique are very essential and important due to original,
meaningful and exact right information through which the developer
(software project team) for set up there plan for making particular
software
...
E: In the view of S
...
in this part the development
team and the project team set a focus for making a particular
software for the desired client
...

These are:
1) interviewing
2) communication
3) presentation
4) site visit

1)

Interviewing: - it is the method by which we collect the
data by a specific communication by the software developer and
the customer
...


2)

3)

Communication:

- it refers a technique for building a
project at the start phase
...
i
...
, software development team and the
customer from the software company view generally we make a
team for the communication purpose
...
i
...
,
software development team and customer
...


4)

Site visit: - it is a very important technique for collecting data
for a specific operation
...


Module 4
System design
1) Discuss the term of system design: - after
getting all information regarding making and implementation of
software from system development life cycle or from any source
which helps to build successful software
...
Design here means that the
structure and all essential steps, which is to be used for making
a particular software
...

In S
...
In view of
S
...

b) ERD (entity relationship diagram)

2) What do you understand by design (in
view of S
...
The genetic
models do not contain process description rather it deals with
product
...

System design tools are basically in two types
...

b) System design tools (data dictionary, process description)
...

b) Data dictionary
...


In 1976 chain, introduced the method of data analysis in which
takes please through out whole development cycle but in
different degrees in detail
...
It starts when a DFD is finished
...
The program structure is
designed from its DFD representation
...
They are used in system
development process
...


Internal entity or transformation process
...
Source process and output are drowning with particular
symbols
...
When a single process connects all data
source with proper arrows
...
A context diagram is decomposed into successfully lower level
in detours
...
It focuses on physical entities involved in the
system under study as well as the readable documents reports and
other hard copy of input and output
...

That indicates a task the system performs
...
Context
level, DFD for payroll processing system
...

ERD is a major data in our project into entities and define the
relationship between the entities
...


2nd entity: - a data relationship is a natural association that
exists between one or more entities
...


4th cardinality: - it is the specific no of occurrence from
one object to another object or one entity to another entity for a
particular description
...
These are:
1) data flow diagram
2) data dictionary
3) data structure diagram
4) structure chart

Data dictionary contain the information about the data of
a system
...
e
...

A data dictionary is organized into 5 sections:
a) Data elements
b) Data flows
c) Data stores
d) Process
e) External elements

Object oriented design (OOD): - in the object
oriented design the analyst consider and implement the
entities in a particular object
...

In the real world scenario this type of design
tools has made its own success
...

In the S
...


Coupling and cohesion: Coupling: - between two methods indicate the degree of
independence between them
...
It is
basically determined by no of parameters that are interchange
while invoking function of a particular module
...
For example- an integer, a float etc
...
Such as a structure in c,
as a record Pascal
...


Cohesion- it is a measures of the functional strength of a particular
module
...
By term functional
independence we mean that a cohesion module performs a single
task for a single function
...

Documentation is a serial part in the S
...
Documentation refers
the whole process relating to the operation, use component Tec
knowledge and other information relating to particular software
...

The external documentation deals with the user manual and
other related information for particular plan (customer)
...


2)

Programming: - these types of documentation help the
programmer and other system level manager to directly or
indirectly involve with programming structure
...
It has some
specific features like system overview, SRS, design, test and
implement
...


5)

Operational: - it maintains the internal working process
including some problem solution for the customer
...


6)

Training: - it basically is a summarized from for training
purpose and user guideline of a software
...


7)

Implementation: - it generally helps to internal process
...
This document is very important for software developer
and customer of how the software implements and run for a
specific purpose
...

1)

System overview: - it is very important step for making
particular software for the software developer
...
it has some
software as well as some hardware information which is used for
the software developer
...
It
has some specific goals which help for making particular software
...


4)

Test plan: - it refers the hole works must be tested with some
specific steps and parameters for deciding correctness for a
particular work
...


6)

Acceptance of test plan: -

this feature include in the
system documentation part to know whether the design
implementation and progress is accepted by designer developer
and some time for user
...
This are
1) availability
2) objectivity
3) cross referencing
4) easy to maintain
5) completeness
1)

Availability: - it refers the documentation should be
available for the analyst, developer and the user
...


2)

Objectivity: -

3)

Cross referencing: - it determines for internal

the objectivity must be focused and clear who
are making the documentation for its specific use
...


communication between to or more module
...

4)

5)

Easy to maintain: -

after complete the documentation
some times it refers in future it may be changed at this time the
documentation should be worked properly and correctly
...
This must be included for making the
documentation successful and complete
...
After
writing the code we have to go through the error checking part to run
the code successfully
...

Coding techniques helps to increase the cast of the
software in the error handing part and the implementation part
...
Some programming language with some specific
programming environment for this we have to know very well the
following objectives in the software coding part
1) Understand very well the design approach
...

3) Select a programming language to achieve a specific task for
client
...

Basically we have two types environment available in
software industry
a) structured programming
b) object programming
The both programming environment has some specific norms in its
own area
...

Mixed language programming: - it is basically a integrated approach for
the software coder to direct and indirect they can change the
environment as it required at the time of operation
...
For example
ERD these type of software like SAP Microsoft lavation
...
Which
helps the coder as well as the user?

Coding structure: - whenever the programmer writes some
codes from the design view
...
Depending programming
language and environment we have to follow norms and syntax of that
programming environment coding principle are –
1) construct the algorithm
2) select the data structure that will meet the need of design,
3) understand software architecture and create a specific interface,
4) keep conditional knowledge as simple as possible,
5) create nested loop that marks their easily testable,
6) select meaningful variable and follow other local coding
instruction,
7) write code that is self documenting,
8) Create a visual laired for easy understanding
...

The term over we can define as some unconditional or conditional,
direct or indirect mistakes from our design phase to implementing
phase in particular software area
...
Fault is a condition for
required achievement of a specific function where as failure is the
inability to achieve a desired goal
...
Its basic objective for checking all parts connecting through
a specific project
...


Unit testing: - in testing methodology first testing is unit testing
...


Ad hope testing: - in ad hope testing we can test whatever comes in
mind for a specific testing
...
In this technique the scope and limitation of software is
absent
...
We
can test without logic
...

Black box testing: - this type of testing for unknown logic structure –
in this the function oriented modules are tested; it includes the
following activities 1) error crossing
2) equivalence class classification
3) boundary value analysis
4) cause and effect graphic
5) domain testing
6) module interface testing
7) Command line testing
...
In this it has basically 4 parts
1) top down testing
2) bottom up testing
3) regression testing
4) smoke testing
1) Top down testing: - in this test each module or class from
the top level of program segment and after that we can add the
first one to next and continue this process until complete
module check
...

3) Regression testing: - this type of testing define and examine
with some existing function and future achievement goal in
specific software regression testing allows the software
development team to ensure that the existing functions and
other modules whether they can use for their coming project or
not
...
This type of testing approach is basically
needed
...
Inside
of project if software development team wants to test some
part of code or module they may up through smoke testing
...

2) Stress testing: - this type of testing help to evaluate the system
performance when it is stressed for a sort period of time
...
has been classing
successfully for a particular solution
...

5) Compatibility: - this type of testing is required when system
interface with other type of system
...

6) Regression: - it is necessary when system is being tested
when a system may be updated from an existing system to fix
some bugs or error in that particular environment
...


8) Maintenance: - this test the all necessary states from design to
implement and determine weather in future all types of
altercation will be available
...

10) Alpha testing: - it is system testing performed by
development team within the developing organization
...

12) Acceptance testing: - this type of testing is done by the users
to determine that software will be accepted or rejected
...
Verification refers to a different set of
authorities which ensure that software which has been built is
traceable to customer requirements
...

It is basically a part of the software quantity assurance
(SQA): - tested approach in the S/EIt includes the following objectivity1) To ensure that product is sofa and result
...

3) To ensure that the product is what the user want
...
It is
longer acceptable to the customer of a particular poor quality
product and then it refers after they have been delivered to
customer
...

Quality planning: - the selection appropriate procedures
and standard form this frame work and adaptation for a specific
software project
...


Quality tools: - an international standard team can be used
in development of a quality management system In all industries
is called ISO (international standard organization)
...
These tools
include –
1) design control
2) product identification and traceability
3) inspection and testing
4) corrective action
5) document control
6) Service training etc
...

Quality assurance activities defines frame work for
achieving software quality which involves with selecting standards the
should be applied for software development process or software
product
...

McCall’s quality factors: - the factors that effect software
quality can be categorized into two groups –
1) Factors that can be directly measured
...

In each case segment the focus is to defect the quality factor in
the software including program data and documents
...
The
main three objectives are that: 1) Operational characteristics
2) Ability to under go change
...

McCall’s quality factor has 3 main partsa) product revision
1) maintainability
2) flexibility
3) testability
b) product transition
1) portability
2) reusability
3) interoperation ability
c) product operation
1) correctness
2) integrity
3) effectiveness
4) reliability
5) usability

Module 10
Software project management
Explain project management: - project management is
the technique of maximizing the provability that a project
developer its goal on time, within the budget and the good quality
...

A common process frame work is selected an appropriate
S/E
...

Project control: - in software industry the main problem of making
a software are –

1) estimate the cost
2)
3)
4)
5)
6)

knowledgeable professional
delivery within time
meets all customer requirement
good quality
Scope for the future
...
We know the main elements of
software project management are –
Project planning: - it has some specific objectives
...

Project scheduling: - it refers the time span or period for a specific
software project
...
Here resource allocation the professional
people and other related categorized are involved
with project scheduling
...
In real world scenario
sometimes the resource are not available as much we want for that point
of view the risk term played a specific job for software developer as well
as the customer
...

Software cost estimation: - it is very important for software project
management to control the overall budget from company side as
well as customer or client SID
...

Quality management: - quality is another key factor for particular
software for a development team as well as customer ideology for
any industry
...


WBS (work break down structure): - a WBS in project
management and system engineering is use to define and group
a project
...

A WBS element may product, data service or any
combination
...
Additionally the key
is a dynamic tool that can be developed and received as needed
by project manager
...

For example- a program a project and contract the project or
contract the WBS is developed by starting with the end objectives
and solve dividing into manageable components in tare-of-size,
duration and responsibility
...
The 100% rule state that WBS includes 100%
of the work defined by the project scope and capture for internal
and external process in terms of work to be completed including
Project management

---