Download hutto puka noidi meka blpn ponnayo and more Study notes Business Ethics in PDF only on Docsity!
Prepared by: Higher Education Qualifications (HEQ) Approved by: HEQ, QDAM (HE) Version 1.0 – November 2017 DCL 1 – Public (Unclassified) 1
Assignment Brief (RQF)
Higher National Certificate/Diploma in Computing
Student Name/ID Number: Unit Number and Title: Unit 34: Systems Analysis & Design Academic Year: 2020/ 2021 Unit Assessor: Buddhini Samarakkody Assignment Title: Evaluation and application of analysis & design methodologies Issue Date: 12 th^ February 2021 Submission Date: 25 th^ March 2021 Internal Verifier Name: Gajhanan V. Date: 24 th^ July 2020 Submission Format: The submission should include the following: Written Report The report should be written in a concise, formal style using single spacing and font size 12. You are required to make use of headings, paragraphs and subsections as appropriate. Any content obtained from outside sources should be referenced using the Harvard referencing system (in-text referencing should be done and the corresponding sources should also be included in the list of references at the end of your report). There is no limitation for the word count of your report. However, you should not need to exceed more than 20 to 25 pages. Unit Learning Outcomes: LO1 Evaluate the strengths and weaknesses of the traditional and agile systems analysis methodologies LO2 Produce a feasibility study for a system for a business-related problem. LO3 Analyze their system using a suitable methodology LO4 Design the system to meet user and system requirements
Prepared by: Higher Education Qualifications (HEQ) Approved by: HEQ, QDAM (HE) Version 1.0 – November 2017 DCL 1 – Public (Unclassified) 2 Assignment Brief and Guidance: Assessment Scenario 1 You are selected to work as an intern for an IT Consultancy firm. One of their clients who currently use traditional analysis & design methodologies and intending to go for agile methodologies, have requested the firm to conduct a study on Evaluating the strengths and weaknesses of both approaches and produce and present a written report to them. Your manager has selected you for this assignment. In the written report, you are required to cover the following: Describe the different traditional and agile methodologies (SDLC models) available along with their features, discussing strengths and weaknesses of each Compare and contrast the strengths and weaknesses of these traditional and agile systems analysis methodologies that you identified Critically evaluate (give your own opinion on) the strengths and weaknesses of these traditional and agile systems analysis methodologies Assessment scenario 2 Consider a business problem scenario of your choice and interest. You may select the business problem that you want to study, from your area of specialization i.e. Software, Networking. You are required to carryout the following and include them in the written report: Explain the background to your business problem and propose a potential solution for it (Note: You may come up with more than one alternative solution if required and applicable.) Do a feasibility study for your proposed solution/solutions to the business problem (Note: Assess at least the Technical Feasibility, Economic Feasibility (i.e. Cost-Benefit analysis) and Operational Feasibility) Evaluate the relevance of the feasibility criteria you assessed above, in terms of your business problem (Note: You should talk about the importance of assessing Technical Feasibility, Economic Feasibility and Operational Feasibility for your business problem) Critically evaluate the strengths & weaknesses of your feasibility study (Note: Talk about what went well and what did not go well with the feasibility study that you did) Next, you are required to perform a Systems Analysis for your selected business problem scenario using a suitable methodology (i.e. Traditional or Agile) and include them in the written report: Use a suitable methodology to review and analyse your business problem scenario. Document your analysis in the written report. (Note: You can use a suitable Traditional or Agile SDLC model) Use suitable fact finding techniques to investigate and identify user and system requirements (Note: You may draw Use Case diagrams if required)
Prepared by: Higher Education Qualifications (HEQ) Approved by: HEQ, QDAM (HE) Version 1.0 – November 2017 DCL 1 – Public (Unclassified) 4 Learning Outcomes and Assessment Criteria of the Module Pass Merit Distinction LO1 Evaluate the strengths and weaknesses of the traditional and agile systems analysis methodologies P1 Discuss the strengths and weaknesses of the traditional and agile systems analysis methodologies. M1 Compare and contrast the strengths and weaknesses of the traditional and agile systems analysis methodologies. D1 Critically evaluate the strengths and weaknesses of the traditional and agile methodologies and feasibility study. LO2 Produce a feasibility study for a system for a business-related problem P2 Produce a feasibility study for a system for a business related problem. M2 Evaluate the relevance of the feasibility criteria on the systems investigation for the business related problem. D1 Critically evaluate the strengths and weaknesses of the traditional and agile methodologies and feasibility study. LO3 Analyse their system using a suitable methodology P3 Review a system using a suitable methodology for a business-related problem. M3 Analyse the effectiveness of the methodology used in providing a solution for a given business context. D2 Justify the choice of the methodology used in the context of the business problem. LO4 Design the system to meet user and system requirements P4 Design a fully functional system to meet user and system requirements for the business related problem. M4 Assess the effectiveness of the system design with particular reference to the methodology used and how the design meets user and system requirements. D2 Justify the choice of the methodology used in the context of the business problem.
Table of Content
Assessment Scenario 1
1 - System Development Life Circle (SDLC)
A system lifecycle model is a graphical and diagram of the software lifecycle. A life cycle model represents all the ways a software product needs to migrate through its life cycle stages. The structure that follows these methods also embraces it. In other words, a life product model maps the various activities from the beginning of software production to retirement. Developmental activity stages can be planned in different ways for different life cycle models. Thus, any element that does not follow a life cycle pattern contains the essential activities of all life cycle patterns, but the action can be performed in a clear sequence of different life cycle patterns. Can do more than one activity at any stage of the life cycle
1.2 SDLC framework includes the following these steps.
System development life circle.
1.3 Describe the different traditional and agile methodologies
1.3.1 Traditional methodologies
Traditional Systems Development The traditional systems development existed prior to the agile systems development. These methodologies include waterfall method, V-model, Rational Unified Process and others. These methodologies are based on the systems development principles that have served as a foundation for the creation of the systems development to date which can be either sequential or iterative. Sequential approach means that the methodology is made up of a series of steps/stages that follow each other sequential. The steps are dependent of each. With the iterative approach, posits that the methodology divides the intended system into a series of versions. After the implementation of version1 the additional work is done on version 2 and the process continues until the completion of the overall system. The emphasis of the traditional development approach is to create ample documentation which serves as a means for communication and traceability of the design. Documentation also plays a vital role in sharing knowledge and keeping tacit knowledge within the organisation. However, knowledge management is of vigorous importance within organizations. Documentation serves as a means of knowledge for newly recruits and any organizational employee who may want to join the systems development team. There is a variety of traditional systems development methodologies that can be adopted within the organisation. They include waterfall, Spiral, V-Model, Rational Unified Process and Rapid Application Development. The traditional methodology is the most commonly used approach by organizations whereby software development activities are completed sequentially.
02 – Spiral Model
- The biggest problem we face with the waterfall model is that the product takes a long time to complete and the software is outdated. We have a new approach to solving this problem, called the spiral model. The spiral shape is also known as the round shape. In this model, we create the application module by module and hand it over so that the customer can start applying very quickly. And we set up this model only when the module is interdependent. In this model, we develop the application step by step, because sometimes the client provides requirements between processes. The different phases of the spiral model are as follow. ▪ Requirement analysis ▪ Design ▪ Coding ▪ Testing and risk analysis 01 - Requirement Analysis ▪ The spiral model process starts with collecting business needs. In this, the following spirals will include the documentation of system requirements, unit requirements, and the subsystem needs. In this stage, we can easily understand the system requirements because the business analyst and the client have constant communication. And once the cycle is completed, the application will be deployed in the market. 02 - Design ▪ The second stage of the spiral model is designed, where we will plan the logical design, architectural design, flow charts, decision tree, and so on. 03 - Coding ▪ After the compilation of the design stage, we will move to our next step, which is the coding stage. In this, we will develop the product based on the client's requirement and getting the client's feedback as well. This stage refers to the construction of the real application in every cycle. And those spirals had an excellent clarity of the requirements, and the design details of an application are known as the build with having version numbers. After that, these builds are transferred to the client for their responses.
04 - Testing and Risk Analysis ▪ Once the development is completed successfully, we will test the build at the end of the first cycle and also analyze the risk of the software on the different aspects such as managing risks, detecting, and observing the technical feasibility. And after that, the client will test the application and give feedback.
03 - Rapid Application development Model.
▪ Application Development (RAD) is a development model that prioritizes faster prototyping and faster feedback over longer development and testing cycles. With fast app development, developers can always make multiple iterations and updates to faster software without having to start a development schedule from scratch. ▪ RAD is a development model once the developers realize that the traditional waterfall development model is not so effective. ▪ One of the major drawbacks of the waterfall model is that once the program has reached the testing stage, it becomes difficult to change the basic functions and features of the software. This gives you software that may or may not fit your evolutionary needs.
04 - Prototype Model
▪ The prototype model requires that before carrying out the development of actual software, a working prototype of the system should be built. A prototype is a toy implementation of the system. A prototype usually turns out to be a very crude version of the actual system, possible exhibiting limited functional capabilities, low reliability, and inefficient performance as compared to actual software. In many instances, the client only has a general view of what is expected from the software product. In such a scenario where there is an absence of detailed information regarding the input to the system, the processing needs, and the output requirement, the prototyping model may be employed.
03 - Lean Development. Lean Software Development is an agile framework based on optimizing development time and resources, eliminating waste, and ultimately delivering only what the product needs. The Lean approach is also often referred to as the Minimum Viable Product strategy, in which a team releases a bare-minimum version of its product to the market, learns from users what they like, don’t like and want to be added, and then iterates based on this feedback. 04 - Kanban Kanban is a visual system for managing work as it moves through a process. Kanban visualizes both the process and the actual work passing through that process. The goal of Kanban is to identify potential bottlenecks in your process and fix them so work can flow through it cost- effectively at an optimal speed or throughput.
1.7 Strengths and weaknesses of Traditional and Agile methodologies.
01 – Strengths and weaknesses of Traditional methodologies.
Strengths
Waterfall methodology I. This model is simple and easy to understand and use. II. The rigidity of the model makes it easy to manage - each stage has a specific distribution and review process. III. The stages of this model are prepared and completed simultaneously. IV. The platform does not overlap. V. The waterfall model works well for small projects where the requirements are clearly defined and well understood. Spiral model methodology I. Additional activation or changes can be made later II. The cost estimate is easy because the prototype building is made of small parts III. Continuous or redevelopment helps with risk management IV. Development is fast and the element is gradually added during spiral development V. There is always space for customer feedback Rapid application development I. Flexibility and adaptability to change II. It is useful when the overall project risk has to be reduced III. It is adaptable and flexible to change IV. Switching distributions is easy because of the use of scripts, high level abstractions and intermediate codes V. Manual coding is declining due to the reuse of code generators and codes VI. There is a possibility of shortcomings due to the prototyping of nature VII. Each stage of RAD gives the client the highest priority functionality
02 – Strengths and weaknesses of Agile methodologies.
Strengths
High flexibility of the project Short cycles and regular iterations allow your project to adapt to the needs of the customer at any time. You do not want to be frustrated if you cannot get the right pitch so invest in a good capo. This makes the development process extremely flexible. High customer satisfaction with the development process. As Agile projects are closely coordinated with the customer, he / she has a strong impact on the development project. Software pieces are constantly delivered in short cycles and customer feedback is always taken into consideration. Constant interaction between stakeholders. When your teams are constantly interacting with each other and with the client, you avoid producing tons of technical documentation, processes, and tools. Every member feels that they are an important part of the team participating in the decision-making process. This stimulates creativity and initiative and gives better results. Continuous quality assurance, attention to detail. The test team must ensure the quality of the product from the earliest stages of rapid development. Since development takes place in a short cycle, testing continues to be dynamic and allows you to produce a good final product.
Weakness of agile methodologies
Problems with workflow coordination. Agile projects involve several small teams working on their own software pieces. They should always coordinate their work with each other, testers and management. Add to that constant interaction with the customer, and you will get a ton of communication management to consider before starting the project. Even though a lot of interaction is considered an advantage of Agile methodology, it may become a weak point due to many factors. Difficult planning at early stages. Planning in Agile development is essential before the process is started. It is important to assess your resources, build up teams, and communicate an overall vision of the project to them before it is kicked off. Professional teams are vital. Agile projects require teams to make serious decisions constantly. It means that only experienced software developers, testers, and managers should be working on the project. This software development methodology provides a very few places for rookies. Lack of long-term planning. A lack of final vision of the project may be disorganizing in some cases. Your project may end up off track if the customer changes his mind too often during the process. And remember, by the end of the project you will have to assemble all those software pieces, which had been changed and adapted a few times over the development cycle and make them work. Also, there will be weak documentation, since the interactions with the customer were mostly verbal.
3. The strengths and weaknesses of these traditional and agile systems
analysis methodologies
Assessment scenario 2
2. Business problem and propose a potential solution
2.1 Hotel and Hospitality Industry.
Three Internal issues in the Hospitality Industry In general, the hospitality industry as well as the restaurant sector tends to get hard when things change. The overall shifts can be as large as globalization. In addition to this, they can also be as specific as local economy and as unpredictable as technology. Moreover, there is also the fickleness of the consumers’ decision- making procedure. No wonder the business managers and owners in the hospitality sector are losing their sleep. 01 Institutional Issues The sector of hospitality is feeling the overall impact of globalization to a huge extent. The restaurants have a great variety of the vendors and other options to make their menus more and more appealing when obtaining supplies as well as ingredients at low costs. Additionally, importing goods or ingredients from other nations has its own risk sets. The risks can be of various factors like a well-publicized incident surrounding contamination. Moreover, there are unfair labor practices, issues which media-savvy consumers find a bit disappointing and other issues related to toxic materials utilized in the manufacturing units. However, cheaper sourcing can be easier particularly in a global economy. Most importantly, the customers have become more selective in case of spending in an alignment along with their values, which keeps on shifting. 02 Financial Issues In case of the hospitality industry, mainly in restaurants and hotels, the financial factor or the economy plays a major role in the determination of both business and personal spending level. Moreover, the tourism-heavy locations, which mean the places where tourists mostly come, this factor holds even better effect than others. In the hotel and travel sectors, the advantages and disadvantages of the global events can have a severe impact on the international spending. This is what makes one of the biggest challenges faced by the hospitality restaurants and industry. Furthermore, when the overall demand of lodging and travelling goes down or get affected, both the profit as well as revenue in the hospitality industry decreases. The profit and the prices slashed try to fill the empty flights and rooms. In addition to this, raising the rates in order to recover the lost profits is a trick in the business, which is done later in the peak seasons.
