IT point

  Extreme Programming Extreme programming was developed by KENT BECK. Extreme programming is a designed to support a small medium software development teams. Extreme programming is a software development methodology which is intended to improve software quality.  Values of Extreme Programming (1) Communication There should be a good communication between the team and client. The entire team members should work together to complete task. (2) Simplicity Team members will focus on things that matters and do not waste time on things that they does not ask for.  (3) Courage Developers should have the courage to take fast decision due to the collective ownership. (4) Feedback Fast feedback will increase the effectiveness of the process.  Example Developers  :     Estimate the user stories and respond with estimations. Customers    :    Test the software and send feedback that will increase the quality. Activities in Extreme Programmi...

 Agile Model Agile means "ability to respond to changes" ,changes from requirements technology and people". Agile model is combination of iterative and incremental process model. This model release software after testing to check whether software quality maintain or not. It provides full freedom to the user to add requirements at any stage after release. Agile model mostly recommend to make critical and risk based software. Examples Extreme  Development, Scrum, Test Driven Development etc. When to Use Agile Model It is used for time critical applications. It is used when new changes are needed to be implemented. It is used to implement a new feature the developers need to lose only the work for a few days or only hours, to roll back and implement. Principles of Agile Model (1) Satisfy Customer Customer satisfaction by early and continuous delivery of valuable software. (2) Welcome changing Requirements Welcome changing requirements even in the late development. (3) Worki...

V model The V model also known as verification and validation. The major point of V model is that it over comes a draw back of waterfall model which you can not go back to previous stage for correction. V model also allows you to test the software at each stage in reverse manner. V model allows you to verify and validate in parallel way. When to use V model  It should be used for small to medium size projects where requirements are clearly defined. It should be chosen when simple technical resources are available with needed technical expertise. It should be used when requirements are clearly defined. Phases of V Model Verification  Verification means, Are we building the product right? (1) Requirement Analysis Requirement analysis also known as requirement gathering. It contains communication with the customer to understand their requirements. (2) System Design  system design contains the complete hardware and communication setup for developing product. (3) Architectural...

 RAD Model RAD stands for Rapid Application Development.  RAD model is adoption of waterfall model.  It aims at developing a software in a short span of time.  In RAD model system developers and users work together.  All the work goes in parallel way in RAD model. When we use RAD model When the project is in under specific time period. When technical risk is seems to be very low. When the user is involve throughout the project. When the whole project is understand properly. Phases of RAD Model   (1) Business Modeling The information flow among business functions is defined by answering questioning like what information drives the business process, what information is generated, who generates the information etc.  (2) Data Modeling The information that collected from business modeling is refined into a set of data objects that are needed to support the business. (3) Process Modeling Any changes or enhancements to the data object sets is defined in proce...

 Topic Outline SRS Purpose Levels of requirements Requirement statement Characteristics Software Requirement Specification SRS is the official statement of what the system developers should implement. SRS is a complete description of the behavior of the system to be developed. SRS should include both a definition of user requirements and a specification of the system requirement. SRS fully describes what the software will do and how it will be expected to perform. Purpose SRS used to know all the requirements for software development and thus that will help in designing the software. It provides feedback to the customer. Levels of Requirements (1) Business Requirement Define the business problems or opportunities about the product. Business requirements define why the software product is being developed. They are the objectives of the customer requesting the development of the software. Users will be able to correct spelling errors in a document efficiently and it will be integrate...

Topic Outline Use Case Components of Use case Actor System Boundary Relationship Example  Use Case Diagram A use case is a pattern of behavior the system exhibit. Use cases are a sequence of actions that the user takes on the system to get the particular target. The use case is a dialogue between an actor and a system. A use case model is a diagram or set of diagrams that together with some additional documentation show what the proposed software system is designed to do. Components of Use Case     (1) Actor An actor is someone or something that must interact with the system under development. Actors are not part of the system usually represented with a stick figure.   An actor may be: People, Computer hardware and devices, External systems Primary Actor Primary actors are completely outside the system.  Acts on the system.  Uses the system to fulfill his/her goal. Secondary Actor Secondary actors often appear to be more inside the system than outside. Help...