Sunday, October 13, 2013
What are two fundamental cryptography principles?
Posted by
Sunflower
at
10/13/2013 06:00:00 AM
0
comments
Labels: attacks, Authenticate, Cryptography, Encrypt, Encryption, Errors, Fundamental, Host, Information, Integrity, Intruder, Messages, Principles, Recipient, Redundancy, System, update, Valid
![]() | Subscribe by Email |
|
Tuesday, August 27, 2013
What are general principles of congestion control?
Posted by
Sunflower
at
8/27/2013 09:32:00 PM
0
comments
Labels: Application, Bandwidth, Buffer, Congestion, Congestion control, Control, Data, Network, Network Congestion, Networking, Nodes, Overflow, Packets, Performance, Principles, Resources, Routers, States
![]() | Subscribe by Email |
|
Thursday, March 28, 2013
What is the basic principle behind Dynamic synchronous transfer mode (DTM)?
Principles of Dynamic synchronous transfer mode (DTM)
- Ring
- Double
ring
- Point
– to – point
- Dual
bus and so on.
Posted by
Sunflower
at
3/28/2013 09:32:00 PM
0
comments
Labels: Application, Circuit, Communication, DTM, Dynamic, Dynamic Synchronous Transfer Mode, Network, Networking, Packet, Principles, Protocols, Quality, Services, Switching, Synchronous, Transfer, transmission
![]() | Subscribe by Email |
|
Thursday, March 21, 2013
What are principles of autonomic networking?
Principles of Autonomic Networking
- Ability to protect itself
- Ability to recover from the faults
- Ability to reconfigure itself as per the
environment changes.
- Ability to carry out its operation at an
optimal limit.
- The internal environment: This includes
factors such as CPU utilization, excessive memory and so on.
- The external environment: This includes
factors such as safety against external attacks etc.
- Sensor channels: These sensors are required
for sensing the changes.
- Motor channels: These channels would help the
system in reacting and overcoming the effects of the changes.
Posted by
Sunflower
at
3/21/2013 09:13:00 PM
0
comments
Labels: Application, Approach, Autonomic Networking, Autonomic System, Design, Environment, Factors, Faults, Functionality, Goals, Networking, Operation, Principles, Requirements, Technology
![]() | Subscribe by Email |
|
Wednesday, January 23, 2013
What kind of testing engines are supported by Fitnesse?
- A
wiki page
- A
testing engine
- A
test fixture
- System
under test
Types of Testing Engines supported by FitNesse
Posted by
Sunflower
at
1/23/2013 04:25:00 PM
0
comments
Labels: Application, Automation, Components, Engine, Engines, FitNesse, Fixture, Format, Java, Languages, Principles, Software System, System, Tester, Testing, Testing Engine, Testing tools, Tests, Tools, Users
![]() | Subscribe by Email |
|
Monday, January 21, 2013
How is test execution done by Fitnesse Testing Tool?
- Wiki page that is
used to express the test in the form of a decision table.
- A testing engine for
interpreting this wiki page.
- A test fixture that
is invoked by the engine and itself invokes the SUT or system under test
in turn.
- SUT(system under test) that is
currently under test.
What kind of engines are supported by Fitnesse Testing Tool?
Posted by
Sunflower
at
1/21/2013 11:57:00 PM
0
comments
Labels: Application, Automated, Automation, Components, Engine, FitNesse, Fixture, Format, Java, Languages, Principles, Programmers, Software System, System, Tester, Testing, Testing tools, Tests, Tools, Users
![]() | Subscribe by Email |
|
Explain FitNesse testing tool? What are principles of Fitnesse?
Principles of FitNesse Testing Tool
Posted by
Sunflower
at
1/21/2013 12:38:00 PM
0
comments
Labels: Application, Automated, Automation, Classes, Developer, FitNesse, Format, Java, Languages, Principles, Programmers, Software System, System, Tester, Testing, Testing tools, Tests, Tools, Users, Web server
![]() | 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 |
|
Tuesday, January 8, 2013
What is Cleanroom Software Engineering?
What is Cleanroom Software Engineering?
Principles of Cleanroom Approach
- Development
of software systems and applications based up on formal methods: Box
structure method is what that is used by the cleanroom development for
specifying and designing a software product. Later, team review is used for
carrying out verification of the design i.e., whether it has been
correctly implemented or not.
- Statistical
quality control through incremental implementation: An iterative approach
is followed in the cleanroom software engineering process i.e., the
software system is evolved through increments in which the implemented
functionality gradually increases. Pre–established standards are used
for measuring the quality of all the increments for making verification that the process is making acceptable process. In case the process
fails to meet the quality standards, testing of the current increment is
stopped and the process is returned to the designing phase.
- Statistically
sound testing: Software testing in cleanroom development process is
carried as a disguise of a statistical experiment. A subset that
represents software’s i/p and o/p trajectories is selected and then
subjected to testing. The sample so obtained is then considered for statistical
analyzation so as to get an estimation
of the software’s reliability and level of confidence.
Features of Cleanroom Software Engineering
- Statistical
modeling
- Usage
scenarios
- Incremental
development and release
- Separate
acceptance testing
- No
requirement of unit testing and debugging
- Formal
reviews with verification conditions
- <3 .5=".5" and="and" delivered="delivered" kloc="kloc" o:p="o:p" per="per">3>
- Incremental
development: Each increment is carried out from end – to – end and in
some cases there is overlapping development of the increments. This whole
process takes around 12 – 18 weeks and partitioning though being critical
proves to be difficult.
- Function
– theoretical verification: A parser may check the constructed program for
syntax errors but it cannot be executed by the program developer. Verification
conditions drive the team review for verification. Verification is
improved by 3- 5 times than debugging. Formal inspections also fall under
this category.
- Formal
specifications: This further includes:
- Statistical
usage testing: It helps in implementing cost effective orientation and
process control. It provides a stratification mechanism to deal with
situations that are critical.
Posted by
Sunflower
at
1/08/2013 03:39:00 PM
0
comments
Labels: Applications, Approach, Cleanroom Software engineering, Cleanroom strategy, Defects, Design, Features, Methods, Prevention, Principles, Process, Quality, Reliable, Software, Strategy, Technology, Verification
![]() | Subscribe by Email |
|