OBJECTIVES OF SOFTWARE ENGINEERING


While developing software we should remember these points in mind, to develop highly recommended software:

  • MAINTAINABILITY: Software is should be maintainable, in the market whenever we launch a new product then the customer will buy it only if it is easy to maintain. That is also a reason why people are using drag & dropping website builders in place of coding, it's only because they found it easy to maintain a website using WordPress, Joomla, ghost, etc.


  • INTEROPERABILITY: Two or more functional units can process data cooperatively when we are dealing with large projects which have integration between different components of a system where the need for interoperability is very high.


  • CORRECTNESS: Customers want an error or bug-free software that processes a user's request in a very fast way and fulfill all of the user's requirements.


  • RELIABILITY: Software should be reliable, it means that the software which a customer buys with their hard-earned money makes the life of a customer very easy to depend upon particular software.


  • PORTABILITY: Software needs to be portable so that it can be used on different platforms with the changing technologies.


  • EFFICIENCY: Software must be very efficient with the user's requirements and future needs.


  • TESTABILITY: Software should be developed in a manner that will be easy to test. Generally, two major approaches which are followed during the development to make the software easier to test are bottom-up and top-down approaches.


  • REUSABILITY: In the cooperative world many time we generally use the component assembly model for development. Where we assemble the common or pre-developed components for the development of a new project. So, we should develop software in such a way that it will be easy to reuse the software for future projects.


  • ACCURACY: It is the major concern of every software manufacturer by a firm, organization, or even a multinational company. If our software is not accurate then will be very dangerous for our reputation and also will adversely affect the number of future clients.


  • ADAPTABILITY: Our software should be very adaptable for the user so that the users will find it easy to change from their present system to the new one developed by us.


To remember these points we have mnemonics:

M.I.C.R. P.E.T.R.A

in which MICR(number on checks) and PETRA(one of the seven wonders of the word)

i.e, we need a MICR check to go to PETRA.



Location: Dewas, Madhya Pradesh, India

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