CouplingCoupling between two modules is a measure of the degree of interdependence or interaction between the two modules. A module having high cohesion and low coupling is said to be functionally independent of other modules. If two modules interchange large amounts of data, then they are highly interdependent. The degree of coupling between two modules depends on their interface complexity.Types...
Monday, 31 March 2014
Cohesion and its type | software design
Posted by Roy on 08:48
Cohesion Cohesion is a measure of functional strength of a module. A module having high cohesion and low coupling is said to be functionally independent of other modules. By the term functional independence, we mean that a cohesive module performs a single task or function. A functionally independent module has minimal interaction with other modules.
Types of cohesion:
coincidental cohesion
logical...
Posted in Cohesion, coincidental cohesion, Communicational cohesion, Functional cohesion, logical cohesion, Procedural cohesion, Sequential cohesion, Temporal cohesion, types of cohesion
Monday, 24 March 2014
Software design and its types
Posted by Roy on 06:25
Software design deals with transforming the customer requirements, as described in the SRS document, into a form (a set of documents) that is suitable for implementation in a programming language. A good software design is seldom arrived by using a single step procedure but rather through several iterations through a series of steps.
Design activities can be broadly classified into two important...
Posted in Detailed design, preliminary design, Software design, Software design and its types
Sunday, 16 March 2014
Formal technique | Formal specification language| Formal requirements specification
Posted by Roy on 06:41
Formal techniqueA formal technique is a mathematical method to specify a hardware and/or software system, verify whether a specification is realizable, verify that an implementation satisfies its specification, prove properties of a system without necessarily running the system, etc. The mathematical basis of a formal method is provided by the specification languag...
Posted in Formal requirements specification, Formal specification language, Formal technique, satisfacation relation, semantic domains, software engineering, syntactic domains
Decision table | Requirement analysis and specification
Posted by Roy on 06:21
Decision table:A decision table is used to represent the complex processing logic in a tabular or a matrix form. The upper rows of the table specify the variables or conditions to be evaluated. The lower rows of the table specify the actions to be taken when the corresponding conditions are satisfied....
Posted in Decision table, notes of software engineering, Requirement analysis and specification, software engineering
Dicision tree | Requirement analysis and specification
Posted by Roy on 04:21
Decision tree :
A decision tree gives a graphic view of the processing logic involved in decision making and the corresponding actions taken. The edges of a decision tree represent conditions and the leaf nodes represent the actions to be performed depending on the outcome of testing the condition.
Example:...
Posted in Dicision tree, Library Membership Automation Software, notes of software engineering, Requirement analysis and specification
properties of SRS documents | SRS documents
Posted by Roy on 00:00
The important properties of a good SRS document are the following:
There are six properties of good SRS document:
1.concise
2.structured
3.black- box view
4.conceptual integrity
...
Posted in notes of software engineering, properties of SRS documents, SRS documents
Subscribe to:
Posts (Atom)
Coupling and its types | software design