How much for this document?1 Graduate Diploma in IT Level 7 GIT 703: Systems Development...

Question

How much for this document?1 Graduate Diploma in IT   Level 7 GIT 703: Systems Development Integration 3      NQF Level 7, 20 credits Assignment 1: Methodology Report  (Worth 20% of final Mark) (20 Marks)   2 Instructions and guidelines for the Assessment: 1. Submission date and time: ___________________________________.   2. The completed assignment must be handed to the lecturer at the beginning of the class  on the due date.   3. Submit a print and bonded copy of your report along with the electronic copy of all work.  The lecturer will inform you how to submit the soft copy.   4. Warning: All media must be virus free!  Media containing virus or media that cannot be  run directly will result in a FAIL grade.   5. You must read and understand Aspire2 International’s policy on ‘Academic Dishonesty and  Plagiarism’. Assignments completed using unfair means or plagiarised will receive a FAIL  grade.   6. The report must have a title page with your name, class and id number clearly printed.   7. Start working on the assignment as soon as it has been handed out in the class. Working  on the assignment right from day one will ensure that it is completed on time.   8. Work through each task, making copies of the source codes, diagrams and output produced  as you complete them as they will be required as part of your submission.   9. Use the right naming and indentation style. Use comments to document each class and  method.     10. Assignments will be judged on the basis of completeness, correctness and clearness. Learning Outcome Targeted: LO 1: Evaluate alternative development methodologies for a software project (e.g. agile,  prototyping, rapid application development, and waterfall)         3 Assignment 1    Introduction    Information and communication technology (ICT) has become one of the most  important component of all contemporary organizations, and so software projects are  planned and executed everywhere, from a non-profit organization to a state of the art  fully projectised organisation. A huge growth in the field of software project  management methodologies have been seen in the recent few years. On the one had  the traditional software projects have seen a huge growth while on the other hand a  lot of new and more complex software projects have been introduced, such a design  of mobile apps, collaborative computing environments, big data projects, and making  of new and efficient hardware to support state of the art user software requirements.  Each approach has its own strength, weakness and suitability for different software  projects. In this assignment you will be researching the existing software project management  methods and compare them based on different criteria. Assessment aims    The purpose of the assessment is to explore different software project management  methodologies. This assignment aims to assess student’s capabilities to understand,  overview, and compare different project management approaches. Assignment deliverable  You will need to submit a written report of no more than 2000 words, answering the  following main issues of the project.  You are required to perform the following tasks and document in the form of a  comprehensive report.  1. Introduction and current state of the art in software project management  methodologies. You must introduce at least 4 methodologies, 2 agile  methodologies and 2 traditional methodologies, you have to mention the pros  and cons of each one.                                              (12 marks)   4 2. Compare agile and waterfall based on the following criteria:  • Adaptability  • Time and cost requirement  • Scalability  • Project team structure  • Stakeholder engagement  • Size of the project       (3 marks) 3. Write some introduction about your industry project, which software  development methodology you are going to use. Justify your answer.                                                                                                                  (5 marks)  Structure and formatting of the written report:  1. The written report must follow the structure given below. • Assignment cover page   • An executive summary  • Introduction and current state of the art in software project management  methodologies  • Comparison of methodologies  • A methodology selected for the industry project.  • Conclusion   • References    2. The report must adhere to the following format:  • Use standard fonts (10-12) for text and heading in Microsoft word.   • Submit as a single Word document.       5 Marking Schedule for Assignment 1   Criteria  Description  Possible  Marks  Achieved  Mark  In tr o d u ct io n  • Introduction to the project management methodology is  correct and appropriate   • State of the art methodologies have been focused   • Formatting, length, and language is appropriate 2 4×2=8  2 C o m p ar is o n  o f  m et h o d o lo g ie s • Correct comparison criteria have been used   • The comparison is fair and clear   1  2 M et h o d o lo g y  s el ec te d   fo r  th e  in d u st ry  p ro je ct  • Introduction about the industry project  • The selected methodology has been stated and related to  the project  • A proper justification has been provided    2 2 1  Total  20

Neha · Accepted Answer

Contents
Executive Summary	2
Introduction	2
Comparison	4
Waterfall Method	4
V-Shape Method	5
Agile Scrum Methodology	5
Lean Software Development	6
Selected Methodology	7
Conclusion	7
References	8
Executive Summary
In this report we will discuss about the software development life cycle and its importance for developing any new product or existing product. The software development life cycle can be defined as a process which is generally followed to develop a software project in an organization, and it consists of detailed plan which helps to describe about how we can develop, maintain, replace or enhance the specific requirement of any software or new software. The life cycle of the software is used to define a methodology which can be followed to improve the quality of the software and the development process of the whole system. In this report we will also discuss about different types of traditional and agile methodologies and their advantages plus disadvantages. 
Introduction
The software development life cycle can be defined as a process which is generally followed to develop a software project in an organization, and it consists of detailed plan which helps to describe about how we can develop, maintain, replace or enhance the specific requirement of any software or new software. The life cycle of the software is used to define a methodology which can be followed to improve the quality of the software and the development process of the whole system. The life cycle of the software development is divided into 6 steps. 
1. Planning and requirement analysis is the first step, and it is the most important and fundamental phase of the whole life cycle. This stage is performed by the senior most members of the halting way she will have direct contact with the customer, sales Department, experts and the market service from the industry. This information will be used to create a plan which will have a basic approach for the project, and it will also help to conduct feasibility study for the product in terms of technicality, operational and economical. The planning can be used to have understanding of the quality assurance and identify all the risk which are related with the project. The technical feasibility study is generally done to provide a definition for different types of technical approaches which can be followed for the implementation of the project which will have minimum risk out of all (Alshamrani, A., & Bahattab, A). 
2. Defining requirements is the second step and once the requirement analysis is done then we'll have document for the product requirements and these requirements will be approved by the customer or the market analyst. This document will be software requirement specification which consist of all the requirements for the product which will be designed and developed during the life cycle of the project. 
3. The 3rd stage is the design of the product architecture in which we will refer to the software requirement specification to design the best architecture for the product. On the basis of the requirements which were specified in the SRS the developer will create more than one design approach which can be proposed and documented in the design document specification. This document will be reviewed by the stakeholders and on the basis of different parameters like the robustness of the product, budget and time constraint, risk assessment and design modularity best design approach will be selected to develop the product. 
4. The 4th stage is the development of the product in which the architecture of the system will be used, and the product will be built. In this stage the programming code will be generated on the basis of design document specification.

1 Graduate Diploma in IT Level 7 GIT 703: Systems Development Integration 3 NQF Level 7, 20 credits Assignment 1: Methodology Report (Worth 20% of final Mark) (20 Marks) 2 Instructions and guidelines...

Answer To: 1 Graduate Diploma in IT Level 7 GIT 703: Systems Development Integration 3 NQF Level 7, 20 credits...

Answer To This Question Is Available To Download

Related Questions & Answers

Submit New Assignment