FORMAL METHODS

In software engineering, formal methods are the same as the system development life cycle that we have discussed in system analysis and design.

  1. Recognization of the need for change: First of all we have to understand what is our need, motive, and expectations behind changing a system partially or fully.
  2. Feasibility study: Here we understand our limitations that till where we can go in a particular dimension it may be in terms of cost, change, people’s resistance, etc.
  3. Analysis of the present system: Then we have to understand the present system first so that we can know the consecutive which might cause by changes made by us.
  4. Design of a candidate system: Finally we have to design the new candidate system for which we have gathered so much pre-requisite knowledge.
  5. Testing and Implementation of the system: Before implementation, we have to test our new system so that we can rectify the bugs and make the system more efficient. The suggestions that we get in testing will be followed in the implementation of the new system.
  6. Post Implementation: For the reason of future up-gradation and updations we will post implement our system.

Comments

Post a Comment

Popular posts from this blog

DESIGN PRINCIPLES

PROBLEM PARTITIONING: Divide the problem and conquer the problem it means to divide the problem into smaller pieces so that each can be captured separately. ABSTRACTION: The process of hiding certain details and showing only essential information to the user. MODULARITY: It specifies the division of software into separate modules which are differently named, addressed, and integrated later on in to obtain completely functional software. STRATEGY OF DESIGN: To design a system, there are two possible approaches- Top-Down Approach: main components and then sub-components designed Bottom-Up Approach: sub-components and then integrate them to obtain the main component.
Read more

COMPONENT ASSEMBLY MODEL

This model follows an object-oriented methodology where the whole system is divided into components, if they are already available in the library then we import them else we have to build them and at last, we construct the system by integrating them. CHARACTERISTICS: Use of object-oriented technology. Component-class that encapsulates both data and algorithm. Component delivered to be reusable. Paradigm similar to spiral model, but engineering activity involves components. The system is produced by assembling the correct components. ADVANTAGES: Time and resource conservative. Having object-oriented methodology. Components are built once and then they can be reused further. Suitable for small to large object-oriented projects. Very low cost in the construction of the system. DISADVANTAGES: Can’t use it for pioneering projects. Needs good planning and design. Needs a clear and complete definition of the whole system before dividing it into components. Need experts to divide the syst...
Read more

SOFTWARE TESTING

Image
It is a process of verifying and validating that software or application is bug-free, meets the technical requirements as guided by its design and development, and meets the user requirements effectively and efficiently with handling all the exceptional and boundary cases. SOFTWARE TESTING STRATEGIES VERIFICATION: It refers to the set of tasks that ensure that software correctly implements a specific function. VALIDATION: It refers to a different set of tasks that ensure that the software that has been built is traceable to customer requirements. Verification -> “Are we building the product right?” Validation -> “Are we building the right product?” TYPES OF SOFTWARE TESTING MANUAL TESTING: Manual testing includes testing software manually which means without using any automated tool or any script. The tester takes over the role of an end-user and tests the software to identify any unexpected behavior or bug. There are different stages for manual testing suc...
Read more