Tuesday, August 20, 2013
When is a situation called as congestion?
Posted by
Sunflower
at
8/20/2013 08:13:00 PM
0
comments
Labels: Communication, Condition, Congestion, Connection, Data, Increments, Input, Links, Load, Network, Network Congestion, Networking, Output, Packets, Protocols, Quality, Queue, Routers, States, Throughput
![]() | Subscribe by Email |
|
Tuesday, January 15, 2013
What is a Cleanroom approach?
- Specification team: This team is responsible for the development and maintenance of the
specifications.
- Development team: This team is responsible for the development and verification of the software.
- Certification team: This team is
responsible for the development of statistical tests and reliability
growth models.
- Errors per KLOC
- Rate of growth in MTTF
- Number of sequential
error free tests.
- Construction of a
structured program
- Designing of
statistical tests: These tests also contribute to the first purpose.
- Software requirements
specification
- Software design and
development
- Incremental software
delivery
- Incremental
statistical testing
- Regression testing
- Software reliability
measurement
- Process error
diagnosis and correction
- Functional
specification: It involves formal design correctness verification.
- Usage specification: It involves statistical test case generation.
- Concurrent engineering
- Step wise integration
- Continuous quality
feedback
- Continuous customer
feedback
- Risk management
- Change management
- Certification and
scheduling parallel development
- Testing cumulative
increments
- Statistical process
control
- Through actual use
- Treatment of the high
risk elements in early phases
- Systematic
accommodation of the changes
Posted by
Sunflower
at
1/15/2013 01:29:00 PM
0
comments
Labels: Benefits, Certification, Cleanroom approach, Cleanroom Software engineering, Design, Development, Increments, Performance, Principles, program, Quality, Requirements, Software, Specifications, Teams, Testing, User
![]() | Subscribe by Email |
|
Monday, July 11, 2011
What is the Incremental Model in Software Engineering? What are its advantages and disadvantages?
When the elements of waterfall model are applied in iterative manner, the result is the Incremental Model. In this, the product is designed, implemented, integrated and tested as incremental builds. This model is more applicable where software requirements are well defined and basic software functionality is required early.
In incremental model, a series of releases called 'increments' are delivered that provide more functionality progressively for customer as each increment is delivered.
The first increment is known as core product. This core product is used by customers and a plan is developed for next increment and modifications are made to meet the needs of the customer. The process is repeated.
ADVANTAGES OF INCREMENTAL MODEL IN SOFTWARE ENGINEERING
- It generates working software quickly and early during the software life cycle.
- Flexibility is more and less costly.
- Testing and debugging becomes easier during a smaller iteration.
- Risk can be managed more easily because they can be identified easily during iteration.
- Early increments can be implemented with fewer people.
DISADVANTAGES OF INCREMENTAL MODEL IN SOFTWARE ENGINEERING
- Each phase of an iteration is rigid and do not overlap each other.
- Problems may arise pertaining to system architecture because not all requirements are gathered up front for the entire software life cycle.
Posted by
Sunflower
at
7/11/2011 01:46:00 PM
0
comments
Labels: Advantages, Architecture, Disadvantages, Incremental, Incremental Model, Increments, Iterative, Product, SDLC, Software, software engineering
![]() | Subscribe by Email |
|