Computing Systems Project- Fabriapp

Catherine McNally BOO754775 Computing Systems COM667 Computing Systems Project FabriApp Project Description My family business, Fabricat Ireland LTD has been in the forefront of the Structural Steelwork Industry for over 15 years. With many contracts being carried out we have site men all over Ireland at the different jobs. Everyday there are phone calls, text messages and emails from the site guys requesting tools, bolts & fastenings, drawings, hire equipment etc. This creates a lot of time spent communicating back and forth with the site staff and creates an unorganised environment. I believe a progressive web application that allows the site men to log-in to request the supplies they need would be extremely beneficial to the company. When the men log in, they would access their specific site and can fill out a quick form detailing what they need and when they need it. If it was drawings, it would ping a message to the draughtsperson in the office and likewise if it was tools or equipment it would go to the admin staff. All the job roles would have their own log in to access their dashboards where they can view their request and tasks. Once the site men have requested an item a ticket would be raised and within their dashboard, they could view what stage the ticket is at e.g. In progress, completed. Not only would the application allow for requests for new items, but the men can request to off hire their tools or machines when they are done with them. The application will have a database which will store all items that have been requested. This would provide administrators with very useful data. If they see that a certain tool is being hired very frequently, they could make the decision to buy the item instead of spending money hiring it every time. Aims & Objectives AIMS Develop an application that enables employees to request items for site specific jobs Minimise the volume of calls and texts coming into the office from site staff Create a more organised approach than the system in place OBJECTIVES Identify key stakeholders in the project Decide upon a software development cycle to undertake Work with stakeholders to gather requirements Design protypes for the application Regularly present progress to gain feedback A mobile application that allows the site men to log-in to request the supplies they need would be extremely beneficial to the company Everyday there are phone calls, text messages and emails from the site guys requesting tools, bolts & fastenings, drawings, hire equipment etc. This creates a lot of time spent communicating back and forth with the site staff and creates an unorganised environment. Aims -A management system to store data Objectives - Review current solutions already available 3 Requirements Gathering & Prioritisation Gathering Strategies Interviews Observation Working in target environment MoSCoW MUST – Requirements are essential SHOULD – Requirements are important but not vital COULD – Requirements that are nice to have WONT – Requirements will not be delivered Requirement elicitation is a fundamental step with any software development. To establish a foundation for the project and to ensure the final products quality and performance, requirements were gathered by the developer with the assistance of stakeholders MUST – These requirements are essential to the project and are mandatory for the success of the product SHOULD – Requirements that are important but not vital. Project success does not rely on these requirements COULD – Requirements that are nice to have. If these requirements are left out there is a low impact on project success. WON’T – These requirements are out of scope and will not be delivered within the specific time frame 4 Functional requirements ID   Requirement   Description   Prioritisation  F01  Create account   Admin must create accounts for employees to gain access to the app   M  F02  Sign in   User signs into their account to access user specific data   M  F03  Log out   The application will allow the user to log-out  M  F04  Change password   Users can change their password   S  F05  Forgot password   Admins can reset forgotten passwords   M  F06  Delete account   User accounts data can be deleted from the system   C  F07  Mobile application   Mobile application to send receive tasks and requests   M  F08  Send requests form  Users will be able to send requests via a quick form   M  F09  Selected personal   All users can select what employee / department they want to send request to   M  F10  Send & receive   Users should be able to send and receive requests from company employees   M  F11  View requests on dashboards  Users can view the status of their tickets and receive updates   S  F12  User dashboards  Visualisation of all tasks to do/ sent and history of previous tasks  S  F13  Employee Photo   Users should be able to upload a profile photo   C  F14  Admin reports   Admin should be able to create reports based on data in the database   C  F15  Notifications   Receive notifications when you have been sent a message or task to complete   S  F16  Content sharing   Users can send site drawings, pictures etc   M  F17  Multiple uploads  Users can upload multiple files or pictures at once to save time   M  F18  Employee directory   Contact information for all company employees will be available   M  F19  Company directory   Contact information available for regular suppliers   M  F20  Holiday requests   Employees can send a request of leave to admins  W  F21  Database   Records of requests will be stored and saved   M  5 Non-Functional requirements ID  Requirement  Description   Prioritisation  NF01  Theme   A consistent theme and colour scheme associated with the company implemented throughout   M  NF02  Navigation & Usability   Application should be easily navigated without prior training   M  NF03  Password security   Passwords must be a minimum of 8 characters and include an upper case letter and a number   M  NF04  Display   Application should display correctly on varying screen sizes   S  NF05  Login credentials   Usernames and passwords will be stored including the ability to change passwords    M  NF06  Accessibility   Application must be user-friendly and no prior training needed. accessible to all abilities   S  NF07  Password masking  Passwords characters are hidden as the user enters   M  NF08  Performance   Reports should not take more than 2 seconds to be presented   M  NF09  Scalability   Large set of users can be added without extra resources or code changes. Room for growth in the database   S  NF10  Access  No data should be accessible without logging in   M  Risks & Prioritisation Risk No Risk Resolution Unmitigated Likelihood Unmitigated Impact 1 Technology uncertainty To allow for ample time for implementation in the project plan 3 3 2 Stakeholder disengagement With the agile method being employed for this project it will involve constant collaboration with stakeholders through the use of regular sprints. This enables for regular engagement and feedback from shareholders 3 2 3 Delays in schedule Utilising the Gantt chart created during the project planning is an essential tool to help define schedules for each task and keeping the project on course 3 4 4 Requirement changes Regular sprints with the shareholders throughout the development process, provides the opportunity to ensure that the needs of the project are correct and being met. 3 4 5 Unclear specification A clear project specification will be developed to ensure all plans constructed are clear and accurate 3 5 6 Issues with code Testing the code frequently for errors and resolving any bugs straight away when they are found 2 6 7 Loss of source code Back up of code regularly. Minimise risk by saving to GitHub respiratory 2 4 8 Hasty design process Reasonable amount of time dedicated within the project plan to the design process 2 3 9 Unforeseen circumstances To a certain degree some things can be unavoidable however to mitigate the risk a suitable timescale has been implemented for the project to be completed 2 3 Carrying out a risk assessment is an essential task in being prepared for potential problems that can occur within the software project. If a potential risk is identified then a mitigation strategy must be in place After risks are identified the process of prioritisation is carried out to determine the likelihood of the risk and the impact it could have on the project Technology uncertainty- Inexperience or unfamiliarity with the chosen technology to implement the project can lead to delays in the project schedule Stakeholder disengagement- Stakeholders play a vital role within this project. Their continuous communication and feedback is fundamental to the success and purpose of the delivered solution Delays in schedule- Falling behind schedule will result in missing deadlines and may lead to an incomplete software application Requirement changes – Major requirement modifications could affect development times and project falling behind schedule Unclear specification – A vague specification or constant changes or editing can prolong the development of the application, resulting in interruption to the timescale Issues with code – With any project issues with code is to be expected and spending time identifying and resolving these bugs can cause setbacks. Loss of source code – Loss of code could be detrimental to the success of the project. Losing progress would be a problem in delivering the application Hasty design process – Design is critical part in the software development and if it is rushed and not properly planned extra programming hours could be spent in the long run Unforeseen circumstances- Both technical and personal issues could affect the scheduled plan and quality of the project. As there is only 1 developer on the project this could be a major risk 7 Likelihood Vs Impact Before Controls After Controls Probability scale: 1 – the risk is very unlikely to happen 2 – the risk is unlikely to happen, but is not unrealistic 3 – the risk is likely to happen 4 – the risk is highly likely to happen Impact scale: 1 – the risk will have little impact 2 – the risk will have some impact, but it can be managed or reduced easily 3 – the risk will have a significant impact on the project 4 – if the risk occurs the project will no longer be viable 8 Software Development Lifecyle Methodology Agile – ongoing release cycles, monitors progress regular, feedback throughout Waterfall – finish one phase move to the next, little room for revision, not flexible Spiral – flexible, passes through 4 phases over and over in a spiral allowing for refinement until complete There are numerous different methodologies that can be used for software projects and each having their own advantages and disadvantages. Therefore carrying out a comparison of the most popular lifecycle models helped decide which framework was most suitable for this project. 9 Chosen method Agile with scrum Centred around constant engagement with stakeholders and continuous improvement Sprints: Product backlog – primary list of work that needs done and maintained (requirements, enhancements ) this to do list is constantly revised Sprint backlog- what the team wants to achieve from the current sprint (user stories) Sprint goal – the product delivered to the end customer It has been agreed that the chosen software development lifecycle for this project will be agile with scrum. Project must be reactive to changing requirements throughout, therefore waterfall is not a suit. Project is not seen as risk-sensitive- spiral is best suited to high risk projects 3` 10 Use Case Diagram Luicidchart used to create UML Employee login – admin verifies credentials User checks send requests- admin can send user tasks User assigns task – send to admin or employee in office User send requests – all required fields must be completed 11 Design LOGIN HOME DASHBOARD TO-DO DASHBOARD TICKET Users will login with the credentials they have been given Dashboard feature – organise tasks and requests 12 Design SEND REQUEST DIRECTORY MY ACCOUNT Send request form – quick & easy Contact info for employees and main suppliers / contractors My account – bio / photo 13 Project Plan Milestones Sprints Stakeholder involvement Extent of progress 14 Possible Software Selection Platform Xamarin Ionic PhoneGap Database MySQL Firebase SQL Lite Proposed technologies for the application Cross platform frameworks Cross-platform development refers to the creation of apps that are compatible with multiple mobile operating systems Advantages & disadvantages Justification of choice 15 Review Prioritisation strategies Plan / Sprints Work products Evaluation Successes Progress to date What could have been done better? Justification 16