The document discusses Assignment 5 on Introduction to IT. It provides details about the steps of the SDLC including feasibility study, requirement analysis, design, implementation, integration, testing and maintenance. It finds that agile methodology is commonly used in industries, allowing for collaboration between teams and no considerable gaps between phases. Key roles in agile include scrum master, team lead, product owner, and independent tester. Jira software can be used for project management and tracking tasks. The document recommends using an object-oriented programming language like Java, which is an industry standard and well-suited for the project.
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0 ratings0% found this document useful (0 votes)
56 views3 pages
Assignment 5 It
The document discusses Assignment 5 on Introduction to IT. It provides details about the steps of the SDLC including feasibility study, requirement analysis, design, implementation, integration, testing and maintenance. It finds that agile methodology is commonly used in industries, allowing for collaboration between teams and no considerable gaps between phases. Key roles in agile include scrum master, team lead, product owner, and independent tester. Jira software can be used for project management and tracking tasks. The document recommends using an object-oriented programming language like Java, which is an industry standard and well-suited for the project.
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3
Assignment 5
Introduction To IT
Registration Number Name
F19605013 Khawaja Muhammad Awais Arif
Instructor’s Name Date Instructor’s Signature
31th Jan, 2021. Ma’am Kainat Zafar
Steps of SDLC: Feasibility study Requirement Analysis Design Implementation Integration Testing Maintenance Findings: If we use the agile methodology which is most commonly used in industries. Agile works through collaboration between different teams that are responsible for end to end development of the project. Does the plane contain gaps? With agile there are no considerable gaps between the phases of the software development. Do any steps or task overlap? Yes steps overlap as different people responsible for different phases continue to work. What guidelines should you follow during system development? And roles needed. The 12 principles of Agile must be followed. The most important points are collaboration, focus on business value, and quality of software. Scrum master, Team lead, Team member, Product Owner, Stakeholder, Technical experts, Domain experts and Independent tester. How might you use the project management software? Jira software can be used for agile. It keeps a tract of the ongoing tasks. The Kanban board is maintained by the team members which gives an idea about the progress of work. Compiler or Interpreter? Its good to use interpreter as it is dynamic. Would you use an object-oriented programming language? Yes software is a collection of objects hence object-oriented programming language must be used. Would you recommended outsourcing parts of the project? Outsourcing can be done. Outsourcing reduces the company cost and helps the company focus on the core business logic. What is necessary to create a prototype of the project? Proper requirement gathering is required for prototype creation. Popular language: Java can be used. Industry expert: Java is industry standard. Experts prefer Java due to its versatility.
Example of program that use this language:
Oracle EBS has Java implementation.
Which language might be best suited to this project?
Java is best suited for the project. Recommendations: The best SDLC model: The Agile model is a combination of an incremental and iterative approach and is focused on fitting in well with flexible requirements. Teams use the agile development methodology to minimize risk (such as bugs, cost overruns, and changing requirements) when adding new functionality.