This is default featured post 1 title

Go to Blogger edit html and find these sentences.Now replace these sentences with your own descriptions.This theme is Bloggerized by Lasantha Bandara - Premiumbloggertemplates.com.

This is default featured post 2 title

Go to Blogger edit html and find these sentences.Now replace these sentences with your own descriptions.This theme is Bloggerized by Lasantha Bandara - Premiumbloggertemplates.com.

This is default featured post 3 title

Go to Blogger edit html and find these sentences.Now replace these sentences with your own descriptions.This theme is Bloggerized by Lasantha Bandara - Premiumbloggertemplates.com.

This is default featured post 4 title

Go to Blogger edit html and find these sentences.Now replace these sentences with your own descriptions.This theme is Bloggerized by Lasantha Bandara - Premiumbloggertemplates.com.

This is default featured post 5 title

Go to Blogger edit html and find these sentences.Now replace these sentences with your own descriptions.This theme is Bloggerized by Lasantha Bandara - Premiumbloggertemplates.com.

Showing posts with label SOFTWARE ENGINEERING. Show all posts
Showing posts with label SOFTWARE ENGINEERING. Show all posts

Sunday, November 20, 2011

System Development Life Cycle(SDLC) Presentation

SOFTWARE ENGINEERING (TESTING)


Testing is a very critical aspect of the software quality assurance (SQA) and represents the ultimate review of specification design and code generation. The design process focuses on the logical internals of the software, ensuring that all the statement has been tested and all functional external i.e. defined input will produce actual result that agree with the required result.


There are two types of testing
1.                  White box testing.
2.                   Black box testing.



WHITE BOX TESTING – It is also called as glass testing. It is predicted on the close examination of procedural details .Here providing test cases that exercises specific sets of condition and for loops tests the logical paths through the software. It demonstrate that each functional operational at the same searching for error in each function.


 BLACK BOX TESTING – This is also called as the behavioral testing and it focuses on the functional requirement of the software. It enables the software engineer to derive set of inputs conditions that will fully exercise all functional requirements for a program. There seta are used to demonstrate that software functional are operational and integrity of external database is maintained. It helps to ensure that the internal operations are performed according to specific and all components have been adequately exercised.

SOFTWARE ENGINEERING (SYSTEM ANALYST)

SYSTEM ANALYST : - A System Analyst is a person whose conducts a study identifies activity and objectives and determine a procedure to achieve the objectives it is a person with unique skills.


ROLE OF SYSTEM ANALYST 
  • AS A CHANGE AGENT
  • INVESTIGATOR AND MONITOR
  • ARCHITECT
  • PSYCHOLOGIST
  • SALES PERSON
  • POLITICIAN
1. AS A CHANGE AGENT :- Analyst replace the old system with new system.

2. INVESTIGATOR AND MONITOR :- Identity the problems and controls the complete project development.

3. ARCHITECT :- Design all the charts required for the system development.

4. PSYCHOLOGIST :- The Analyst can understand the problem of the developer psychologically.

5. SALES PERSON :- Analyst sales the project.

6. POLITICIAN :- Because he has to interact with different levels of managements.

SOFTWARE ENGINEERING "SOFTWARE TESTING"

Testing is the process to uncover all the errors.


TESTING OBJECTIVES:-
1.       Testing is the process of executing the program to find all the erros.
2.       A  Group test has a high probability of finding errors.
3.       A Successful test  uncovers all the errors that have not been found .

TESTING PRINCIPAL:-
·         The Test should be according to the customers requirement.
·         There should be a planning for testing before starts.
·         The pareto principle implies that 80 percent of the errors uncovered during testing will likely be traceable to 20 percent of all the program component.
·         Testing should be begin “in the small” and progress towards testing “in the large”
·         Exhaustive testing is not possible . it is imposible to execute every combination of paths during testing , it is possible however to adequately cover program logic and to ensure that all the conditions in the component level design have been exervised.
·         To be most effective , testing should be conducted by an independent third party.

SOFTWARE ENGINEERING (SOFTWARE CRISIS)

SOFTWARE CRISIS CAN BE CLASSIFIED IN TWO WAYS




  • FROM PROGRAMMERS POINT OF VIEW
  • FROM USERS POINT OF VIEW 
FROM PROGRAMMERS POINT OF VIEW:-
  1. PROBLEM OF COMPATIBILITY
  2. PROBLEM OF PORTABILITY
  3. PROBLEM OF DOCUMENTATION
  4. PROBLEM OF PIRACY OF SOFTWARE
  5. PROBLEM IN COORDINATION TO WORK WITH OTHER PEOPLE
  6. PROBLEM THAT ARISE DURING ACTUAL RUN TIME IN THE ORGANIZATION
  7. PROBLEM OF MAINTENANCE IN PROPER MANNER.
FROM USERS POINT OF VIEW:-
  1.  HOW TO CHOOSE SOFTWARE FROM TOTAL MARKET AVAILABILITY
  2. HOW TO ENSURE THAT WHICH SOFTWARE IS COMPATIBLE WITH OUR HARWARE.
  3. PROBLEM OF VIRUSES.
  4. PROBLEMS OF SOFTWARE BUGS.
  5. CERTAIN SOFTWARE RUNS ON SPECIFIC OS.
  6. PROBLEM OF DIFFERENT VERSIONS OF SOFTWARE.
  7. SECURITY PROBLEM FOR PROTECTED DATA IN SOFTWARE.

3.SOFTWARE ENGINEERING (RAD MODEL)

The Rapid Application Development model is incremental software development cycle,it is higher speed adaptation of linear sequential model in which rapid development is achieved by using component based construction.the work is divided into sub tasks. Each sub task is assigned to a different team, so application development will be fast.

It performs the following steps

  • COMMUNICATION 
  • PLANNING
After planning each team performs sequentially the following task

  1. MODELING
  • Business modeling
  • Data modeling
  • Process modeling
     2. CONSTRUCTION 
  •       Code generation
  •       Testing
     3. DEPLOYMENT
In this the product dilivers to the customers

2. SOFTWARE ENGINEERING (WATERFALL MODEL)

WATER FALL MODEL

1. COMMUNICATION 
  • PROJECT INITIATION
  • REQUIREMENT GATHERING
 2. PLANNING
  • ESTIMATING
  • SCHEDULING
  • TRACKING
3. MODELING
  • ANALYSIS
  • DESIGN
4. CONSTRUCTION
  • CODING
  • TESTING
5. DEPLOYMENT
  • DELIVERY
  • SUPPORT 
  • FEEDBACK

ADVANTAGES AND DISADVANTAGES

ADVANTAGES
  1. Oldest and simlest method
  2. useful in situtation where requirements are fixed
  3. it is a procedural model
  4. it provides better quality
  5. it is the sequential approach of software development
DISADVANTAGE
  1. Real projects rarly follow this model
  2. difficult for customers  to state all the requirements in advance
  3. customers must have patience
  4. it takes long time in software delivery


1.SOFTWARE ENGINEERING (PROCESS MODELS)




Your Ad Here



It defines the set of activities ,actions, tasks,milestones and output products required to develop high quality software. it provides stability ,organization and control for the activities. these are also called prescriptive process models there are many models but generic framework activities are same for all.
SOME PROCESS MODELS ARE:-
  • WATERFALL MODEL
  • INCREMENTAL MODEL
  • PROTOTYPE MODEL
  • RAD MODEL
  • SPIRAL MODEL
  • WIN WIN SPIRAL MODEL
  • COMPONENT BASED MODEL 





Your Ad Here

Share

Twitter Delicious Facebook Digg Stumbleupon Favorites More