Your main task is to perform requirements analysis and project planning for problem description below.
Ø An overview of requirements including
· At least 10 user stories that summaries the key functional requirements of the system
· At least 3 use cases, each corresponding to a particular user story. Pick the more complex user stories for this purpose
· A UML use case diagram, showing which actors are involved in each function of the system
· At least 3 usability requirements, 3 performance requirements, and 3 reliability requirements
Ø A plan for the development of system including
· Work breakdown structure based on user stories
· An AON or AOA graph incorporating duration estimates and dependencies
· Identification of the critical path and estimate overall project duration
Exercise 1 1 Overall Task You will create a set of requirements and planning documents, manage them using Git. Your first step is to create a new empty Git repository. All your subsequent work must be added to his repository, and the repository itself will be what you submit. 1.1 requirements and planning Your main task is to perform requirements analysis and project planning for problem description below. · An overview of requirements including · At least 10 user stories that summaries the key functional requirements of the system · At least 3 use cases, each corresponding to a particular user story. Pick the more complex user stories for this purpose · A UML use case diagram, showing which actors are involved in each function of the system · At least 3 usability requirements, 3 performance requirements, and 3 reliability requirements · A plan for the development of system including · Work breakdown structure based on user stories · An AON or AOA graph incorporating duration estimates and dependencies · Identification of the critical path and estimate overall project duration · A plan for user of version control throughout the project · What branches will you need, and what for? · When should they be created, and when should they be merged and pushed? · Show the Git command that the development team will use, assuming everything goes well 1.2 Version Control Commit the above documents to the repository as you create and modify each one, not all at once at the end, the marker will examine git log to verify. 2 Problem Description You are performing requirements and planning work for a software system to control key parts of an Antarctic base. The intention is for the system to oversee as much of the operation of the base as possible. The requirements for this system are not yet know You may assume that all equipment is base network-linked so it can be accessed by software/ Key details and background information on the base itself · Base is located in the middle of continent, on a featureless ice sheet that stretches from horizon to horizon. It is one of the most inaccessible and inhospitable parts of the world. Temperature can reach -60 °c with frequent blizzards. In winter, the sky is dark 24 hours per day for several months. In summer the sun remains above the horizon 24hours per day · Base itself is a small town, populated by scientists, engineers and service workers of different type wit highly skilled. There is data collection to be done(the core scientific mission), along with checking and maintenance of the various structures and systems in the base, and more mundane tasks like food preparation · The base has solar panels, a single wind turbine, a large battery, and backup diesel generators. The win turbine must be “parked” in the event of a blizzard to avoid damage · The base has telecommunications equipment to maintain a link to the outside world, and various instruments to monitor the weather, the ice, the Earth’s magnetic field, etc · There are assorted vehicles that can be used to travel around and outside the base. It is vitally important to keep track of where these vehicles are at all time, in case a rescue is needed 3 Marking criteria I. Planning · 3 marks – work breakdown structure · 3 marks – AOA/ AON graph · 2 marks – identification of critical path and overall duration II. Functional requirements · 4 marks – user stories · 4 marks – use case diagram · 5 marks – written use cases III. Nonfunctional requirements · 3 marks– usability · 3 marks –performance · 3 marks– reliability IV. version control · 5 marks –actual use of version control · 5 marks –planned use of version control