BUSINESS AREA ANALYSIS

It consists of a set of steps needed to analyze a business concerning its changing requirements.

  • ENTERPRISE ANALYSIS: Collection of pre-project activities that leads to up to project selection guided by the business analyst. It enables us to make a better understanding of our position in different dimensions of business which will help us in making more business suitable decisions. Usually, it is done by considering project reports and onsite observations.
  • REQUIREMENT ANALYSIS: Define tasks and resources which are associated with the planning and management of a system from the user, customers, and other stakeholders. We have to think about our future expectations and based on that we make a conclusive requirement list. This list will be further used as a reference in board meetings and a comparison of different time periods.
  • REQUIREMENT ELICITATION: Researching and discovering the requirements of a system from the user, customer & other stakeholders. Elicitation is just like a fact discussion meeting where everyone gives their views, facts, and thoughts about a general requirement in the requirement elicitation.
  • REQUIREMENT ANALYSIS & DOCUMENTATION: Stakeholders analysis, structure and specify the design & implementation of a solution. It is a kind of documentation of our requirements which we get to know in the elicitation phase. We do this so that our requirements can reach out to high-level officials in a well-documented and structured format so that it will become easy for them to act on our requirements.
  • REQUIREMENT COMMUNICATION: a collection of activities for expressing the output of the requirement analysis. It consists of board meetings, group discussion sessions, and joint application development (JAM) sessions where all dignified official and the management team communicated with each other, understand requirements, prioritize the needs, and tries to reach a final decision.
  • SOLUTION EVOLUTION & VALIDATION: Ensures that the solution should be able to meet the stakeholder’s objectives. It consists of the final and internal process where management persons decide what to do next for a particular requirement. Their decision will be recorded as a final conclusion in the required report and stored as a future reference.

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