1Q: Differences between all the SDLC models Sr. Name of No Models Features Merits Demerits Area of When to Risk Application use? Management a)Whenever we are developing a small b)Not a good application model for we go for complex waterfall & object model. oriented projects. b)when we have a short c)poor term project. model for long & c) when we ongoing are sure that projects. the requirement d)No never change a.)Require ments are very clean and fixed. a)No overlapping between stages. b.)No b) poor Quality assurance. a)In iterative model we are building and improving the Product step by step. a)Each phase of an iteration is rigid with no overlaps. b) In iterative b) costly system architecture a)Require a)Lack of ments of effective the communicati complete on. system are clearly defined b)Faulty and methodology. understoo d. . 1 Waterfall Model a)Sequential a)It is simple to Process. understand &use. b)Top to down approach. b)Every phases fully dependent on previous phase. c)SDLC based process. d) Used in software development process. c)It is basically used for small projects. e)It provides structured approach. 2 Iterative model a)Iterative development is way of breaking down the software development of a large application into smaller a) High amount of Risks. backtracking model less a)Iterative Application development is a software development method. which users and designers see as equal ambiguous requireme nts. c.)project is short. d.)client has high confidenc e in the organizati on. c)The continuous requirement nt change. d)relatively long stages. e.)Organiz ation has experienc e of similar projects. the system ensures that the end users constantly work with the system a)Spiral model is very widely a)When costs and risk eval- a)Risk management encompasses . detected systems. a)Should be used when the desired system needs to have a lot of Interaction with end user. d)Lack of unified tool use. b) In iterative because not development all requirfeature code ements are is gathered designed. prototype -customer c)Incomplete evaluation. up front for developed the entire and tested in life cycle. time is spent on or design more time is given issues may arise for designing. e)poor Requirement gathering. c)poor documentatio n. Leading to better complexity solutions.2 chunks. Documenting and 3 Prototype model 4 Spiral model b)The I stand for developing in iterations along with the user and gradually expand to a larger utility. original -build plans. c) Major requireme nts must be defined. is when the not always desired Preferred by the developer system . a)should a)Too much be used involvement of client. a)The a)High amount a)Can be a diagrammati of risk analysis costly cally hence. repeated cycles a)It is a a)Users are a)Leads to system actively implementin development involved in the g and then method in Development. avoid model to Partners. of the c)Steps of system model: d)Missing scope of the -requirement functionality can may expand -gathering be identified Beyond -quick design easily. b) Project is big. Much earlier. repairing which way of a prototype b)Errors can building model . needs to have a lot b)Too many b)It ensures of inter. b) Accepb)practically table c)Quicker this methodprototype is user feedback is ology may Finally available increase the achieved. application may cause application.changes can that the end disturb the actionwith users rhythm of the end user constantly Development work with b)it team. of at least a)High amount of risk analysis hence. complex. b) Project's success is highly dependent upon risk analysis phase. Documentation control. three process: -risk b)For assessment medium to -risk high risk evaluation projects. The phase in this approach is same as the phase in the spiral approach. c)identify and resolve risks use.-Risk ements are management. b) Determine objective c)software is &identify produced alternative early in the Solution. Develop lifecycle c)Project’s objectives success is (LCO highly milestone). . development team and the customer hold b)Risk analysis requires highly Specific expertise. The WinWin approach is generally used when you have timebound release. dependent prototypes. used in the software industry b) For medium to high –risk Projects. and analysis specification phase. appears like a spiral b)Strong with many approval and loops. time of the identifying d) Additional the Functionality requirements can be added at a . c)Does not work well for smaller Projects. feasibility of an b)Risk appropriate analysis family of requires multimedia highly applications) specific Cycle 1. a)Risk Analysis requires highly expertise. .3 representation 5 Win win model nice of risk is of a model Enhanced. a)The WinWin spiral approach is an extension of the spiral approach. a)Can be a a)Cycle 0. expertise. s for individual d)Doesn’t applications work well and verify for smaller the existence projects. &risk mitigation c) Requir. b) Good for large and mission-critical projects. c) Strong approval and b) Difference documentation is that at the control. on the risk plans.. software life Cycle. the later date. costly Determine model to the use. d) Significant changes are expected. uation is important. avoidance of Risk is enhanced. high skilled availabilit developers/ c)It should y of designers. b)In RAD model the components or functions are developed in parallel as if they were mini projects c)The development s are time boxed. be used only designers if the budget for d)High permits use modeling dependency of automated and the on code budget is modelling generating high skills tools. and performance is to be achieved through tuning the interface to system components . It is a type of incremental model. c)When technical risks are high RAD may not be a suitable option. d)This may . d) This can quickly give one feasible architecture for each application. 6 RAD model a)RAD model is Rapid Application Development model. a)Reduced development time. delivered and then assembled into a working prototype. be used if there’s high b)It availability should be of designers used if c)Requires for there’s highly modelling. a)RAD should be used when there is a need to create a system that can be modulariz ed in 2-3 months of b)It should time.4 discussion and negotiate on the requirements that need to be included in the current iteration of the software. enough to afford e)Inapplicabl d)RAD their cost. a)Depends on strong team and individual b)Increases performance reusability of s for components identifying business c)Quick initial requirement reviews occur b)Only d)Encourages system that customer can be feedback modularized can be built using RAD a)RAD should be used only when a system can be modularized to be delivered in incremental manner. e to cheaper c)RAD sh a)RAD requires sufficient human resources to create the right number Rad approach does not workproperly b)if high performance is a major issue. new model is also delivered emphasis on changes a type frequently necessary b)Business are needed of Increment (weeks rather designing agility is to be al model. of new d)Each d)Regular c)Only increment release is adaptation to senior s that are be possible while an application heavy uses a new technology. communication. SDLC model should be chosen only if domain experts are available with relevant business knowledge. a)Agile a)Working a)There is a)Superior a)When development software is lack of ROI. than months). want.5 the customer something to see and use and to provide feedback regarding the delivery and their requirements 7 AGILE model projects as cost of modelling and automated code generation is very high. c) It reduces freedom developed in conversation is risk. a)Very large software system b) Large development team. agile gives incremental. representati environment. excellence and that they frequency good design. The b)Software is b)Face-to-face on. c) Scope creep. implement documentati ed. the best form of b) The to change rapid cycles. implement releases with ve is not ed at very each release c)Continuous clear what little cost building on attention to final because of previous technical outcome the functionality. c) This cooperation taken off it create a New results in between track if the sustainable changes small business people customer development can be incremental and developers. ould be chosen only if resources with high business knowledg e are available and there is a need to produce the system in a short span of time (2-3 months). project can d)increases is very Close daily easily get productivity) important. . d) Distributed development environment. and embraced. e)Even late changes in requirements are welcomed programmer s are capable of taking the kind of decisions required during the developmen t process. The QA Tester will work with their fellow testers and Senior tester to ensure quality testing and bug reporting is maintained throughout the product’s entire testing process. b)To implement a new feature the developer s need to lose only the work of a few days. to roll back and implement it. The QA analyst will be required to analyze user requirements. unless combined with experienced resources produced. Understand and document procedures Develop publish and implement test plans Write and maintain test cases . Hence it has no place for newbie programmer s. Extreme Programmin g (XP) is currently one of the most well-known agile development life cycle model changing circumstances.6 thoroughly te sted to ensure softw are quality is maintained. It is used for time critical applications. Q:-Find job profiles for QA Tester and their role & responsibility? Ans:-QA tester role & responsibilities: The QA Tester will follow a documented test plan and be responsible for the reporting of clear and very detailed bug reports. or even only hours. and execute test case scenarios Analysis of test results leading to defect isolation and resolution. and ability to interface with the client Locations: Bengaluru / Bangalore Experience: 4 . Design. QA. Software Testing. Developing high-level test design and planning documentation. JIRA .7 Create and maintain test data Clearly document and re-verify all defects Document test results Analyzing the requirements for multi-tier architected web-commerce applications from industry standard design documents. Job Profiles for QA tester: 1) Senior Tester (QA) Company: WeSucceed Solutions India Pvt Ltd Job Description Strong in manual testing Good to have some exposure to Automation Good experience with Jira Provides time / resource estimates for assigned tasks. demonstrated influencing skills. Test Analyst. code. May provide time / resource estimates for assigned projects.6 years Keywords / Skills : Tester. Manual Testing. Strong verbal and written communication skills. test. etc. Regression Testing. System testing. functionality. Excellent English language skills (written and verbal) required. log the defects and track in the Test Management Tool. Excellent troubleshooting and problem solving skills Attention to detail.)\ • Validate website security • Ensure Visual Regression (Against mockups. Functional testing. – Experience Inspecting. Compatibility testing. API testing. – – – – Firefox Web Developer extension. Firebug. Comfortable in highly-collaborative. Pingdom Website Speed Test. platforms. Load testing and stress testing in mobile handsets and web based applications. Retesting. wireframes etc) • To execute the Test cases.8 Role: Software Test Engineer Industry: IT/ Computers . team-focused environments.Software 2) Opening of QA (manual Tester Worked on CMS ) Profile Company: Apex Services Job Description: • Work alongside software developers and designers to understand features and technical implementation • Testing various websites across multiple browsers. Pune . Locations: Chennai. (content/media using Google's Page Speed Insights. Performance testing. and devices using tools • Check for accessibility. Key Skills Needed: – 2-4 years of web QA software testing experience or equivalent combination of education and experience. debugging. Feature testing. etc. navigation. • Extensive experience in Sanity testing. usability. and profiling WebPages: Chrome Developer Tools. and flow • Verify HTML/CSS code validates with W3C guidelines • Check page download speed. Manual test engineer.Software Salary: 2.Manual tester worked on CMS ( Content Management System) based Technology (no fresher) . CMS. QA.9 Experience: 2 . QA. Automation. Salary .12 Years Relevant exp. Content Management System. in Quality Analyst Profile. Manual testing. 2Yrs of exp.Max 30000 CTC can be offered ( Including PF and Insurance) + Mediclaim + Cab Facility.4.5 years Keywords / Skills :Manual Tester. Quality Analyst. Automation tester.: 4+ Yrs. Wordpress. Test engineer.5 years Keywords / Skills : Manual Tester.00 . Locations: Navi Mumbai. Interview location: Bangalore . Quality analyst Role: Software Test Engineer Industry: IT/ Computers . Min. testing. Joomla Education: Any graduate Function: Manufacturing/ Engineering/ R&D Role: Quality Assurance/ Control Industry: Recruitment/Staffing/RPO 4) Immediate_ Documentum QA Tester Company: Pyramid IT Consulting Private Job Description: Profile Documentum QA Skills Documentum.Mandatory Total Experience: 5 . Mumbai Experience:2 .00 lacs 3) Opening of QA (manual Tester Worked on CMS ) Profile Company: Apex Services Job Description . Experience:3 .. quality Function: • IT • Retail Chains Role: • Quality Assurance Executive • Quality Assurance . M.3 . .Good understanding of database concepts & SQL queries .. MCA etc. preferred Keywords / Skills :Documentum.10 Work Location: Bangalore Education: Technical undergraduate degree B.7 years of overall IT experience and minimum 2 years as QA Lead Project management and team handling skill Good understanding of database concepts & SQL queries Work location: Noida. QA. "SAP BO". QA Test Engineer Role: .Strong knowledge on Data Warehouse & BI Tool (SAP BO) with good analytical skills .5 years of overall IT experience and minimum 2 years as QA specially report testing .7 years Keywords / Skills : "Data Warehouse". "quality assurance".Good communication and articulation skills QA Lead: 5 .Strong working knowledge of standard QA principles. Tech.Good knowledge on Unix commands .Tech.Manager • Quality Assurance/ Control 5) Opening for QA Analyst(Tester)/QA Team Leader for Noida Location Company: Ashayam Consultancy Services Private Limited Job Description: QA Analyst (Tester): Mandatory Skills .Experienced in developing and delivering automated testing of reports . I18n process typically involves the following tasks. Externalizing of strings. >Internationalization testing is the process. graphics. Internationalization is a process of designing a software application so that it can be adapted to various languages and regions without any changes. which ensures that product’s functionality is not broken and all the messages are properly externalized when used in different languages and locale. Ans: Internationalization testing: It is a type of non-functional testing.11 • Software Engineer/ Programmer • Team Leader/ Technical Leader • Software Test Engineer • System Administrator Industry: • IT/ Computers . I18N –Testing The focus of i18n testing is as follows: . >The main purpose of internationalization is to check if the code can handle all international support without breaking functionality that might cause data loss or data integrity issues. Numeric. because there are 18 characters between I and N in Internationalization. Time.Hardware • IT/ Computers . Internationalization testing is also called I18N testing. etc) Changing the Collation /sorting functions Internationalization testing is the process of verifying the application under test to work uniformly across multiple regions and cultures. Changing the logic of all the formatting functions (Date. Selecting code page and defining code page conversions Modifying all the text manipulation functions to be aware of the code page. Currency. icons. texts etc.Software Q: Performing internationalization testing on your graduation based project. updating. hotels. graphics issues or other visual problems. 1. this includes testing the product behavior in identifying and initializing from its language environment and its ability to customize to that environment. . they have large scope of growth. Interoperability testing: It ensures that the software interacts properly with targeted platforms. cities. news etc. Now days when everything is online. Functionality testing: Functionality testing is the core area of i18n testing . applications (and versions) and so on. 1. Admin can manage the user. areas. The system is very useful for the companies who develop apartments. so naturally. villa and other residential properties. updating. reports. It involves verifying the culture specific information such as date/time display.2 Project Scope The real of the World Wide Web have spread across millions of household. Usability testing: It evaluates the ease of use of the system (optional) Installation testing: Testing to ensure if the product installation messages are displayed in a corresponding language when installing the application on a dedicated server. 1. This website is a online real estate management through which individual buyer can maintain their property document keeping and managing property registration and also manage all the adding. These applications are not widely popular but in future. which need to be considered in making the new system.3 Importance of the Project : In this we have discussed the various issues.12 Compatibility testing: Testing the product for language compatibility. or buy using this. deleting the asserts and some of its tasks. Internet has become by far the best platform for real estate marketing today. deleting the asserts and some of its tasks. User interface Validation: To check for visual problems such as text truncation or overlap.1 Project Purpose This site is an Online Real Estate website through which a user can access its information and manage all the adding. which are important for the new system to fulfil. how is it possible that real estate left web application behind? There are lot of real estate companies who advertise their property online so the idea behind developing this website is that their property can also sell. The Admin can change the updates the information regarding property selling and buying. operating systems. There are the objectives. These are: Easy & quick retrieval form large volume of records: The new system should not only ease the retrieval of the information but also help in quick retrieval of the required information.It typically includes running the whole functionality regression test on different language environments and exercising the interface with native language strings. states. These checks can ensure that the data being entered is free from inconsistencies and errors. To reduce redundancy: The new system is also required to reduce the redundancy of the work. The Admin should have all type of authorities. To reduce paperwork & hence the storage space: The new system is required to reduce the paperwork and also to decrease the requirement of storage space required to store these papers and files. The Admin can add. Because here user buy and another user build the home. The Admin should maintain property. It should be less time consuming in terms of data to be input. which will help in retrieval of information as well as its storage. The access right may be different for different people i. areas. The user can first register to itself for selling or buying any property. Product Functions: . delete. The user should have a convenient way to make data entries as well as in extracting the required information. maintenance of all these copies to make sure that they contain up-to-date and accurate information. cities. Decreasing the coping or noting errors: There must be reduced errors due to coping and noting by applying different checks to the data being entered. There is no guarantee.13 To save time: The new system must decrease the wastage of time of the user in searching activities. Thus inconsistencies that are quite common in manual system can be reduced to a great extent. Accuracy: The level of accuracy in the proposed system cannot be decided. edit the state.e. By avoiding the redundancy it will eliminate another common problem. Project Goal: Planned approach towards working: the working in the organization will be well planned and organized. people may be given access to the data only if needed. Project Objectives: The system should have a login. The data will be stored properly in data stores. As all the people can have access to the software it will reduce the need to keep copies of the same on paper. data that needs to be extracted. The reason for the increased reliability of the system is that now there would be proper storage of information. Reliability: The reliability of the proposed system will be high due to the above stated reasons. Admin identify property type as it is home or shop. A login box should appear when the system is invoked. Reliable alterations thus reducing inconsistency: The alterations in data can be done reliably and there is no need of making the same alterations to different copies of each individual as any individual can use the sane copy. news reports of property and manage the user and check the feedback from the users. developed and implemented based on the software requirements specifications document. edit or delete the cities. Two id’s with same name should not be registered. End users should have basic knowledge of computer and we also assure that the users will be given software training documentation and reference material. Every user should sign up. The product must have an interface which is simple enough to understand >Dependencies: All necessary hardware and software are available for implementing and use of the tool. Improve requirement accuracy: Industry-unique collaborative storyboarding improves accuracy by promoting effective communication. Administrator id is primary and can never be changed. . Admin should be able to delete unwanted users. Admin should be able to add. The proposed system would be designed. After submitting registration form. if they want to use the application.3.3 Assumptions and Dependencies: >Assumptions: The code should be free with compilation errors/syntax errors. Admin should be able to see user’s password in case of password forgotten.14 Our system must save time and money: Accurate upfront software requirements definition helps ensure your team works on the business problems that matter most. Admin provide all the information about the property. only admin should validate after checking every information. Admin should be able to add.. edit or delete the property information. User need the number of the receipt in order to use the software with registration. Password can be changed by admin for admin id. User should be able to update their personal information. Users can should be only able to see the information of the Property selling and buying. The system is not required to save generated reports. User should fill a registration form to get their validation to use the software. Admin should be able to add. >Functional Requirements Both administrator and user must have login id to use the application. 2. edit or delete the states. There should be a difference between the options of customer and admin registration. Reduce rework: Early validation and agreement by stakeholder’s means development and quality teams spend less time on rework. 1. >Security User access to the information can be limited by the administrator according to the privacy of the data. The Real Estate Management System will be error free software and easy to use. • Web Scripting: PHP. PHP. Load time for user interface screen shall not take longer time. >Reliability Specify the factors required to establish the required reliability of the system software at the time of delivery. >Non – Functional Requirements The Various Non – Functional requirements are :- >Performance Performance defines acceptable response times for system functionality. >Portability Real Estate Management System shall run in a Microsoft Windows environment with architecture as MVC.15 >User Requirements User must have the knowledge about the computer. • Back end: MySQL. User interface must provide feedback.5 Tools & Technologies Used Tool used Front-end Tool: Back-end Tool: Technologies Used • Front End: HTML and JavaScript.DREAMWEAVER 8 SQL Server(Wamp) . Knowledge about operating the Real Estate Management System Application. 16 Home page Registration Page . 17 Property Found Upload Property detail Edit user profile . 18 Manage User Dat . 19 abase Detail .