Foundation Degree IT Project Milestone 2: Research and Analysis.

Slides:



Advertisements
Similar presentations
GCSE PROJECT GUIDELINES Use this presentation to make sure you have the correct content for you project - click on.
Advertisements

Software Engineering COMP 201
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 8 Slide 1 System models.
Revision Session 1.UML Overview 2.Detailed software design : operation specification, designing for re-use.
System Design and Analysis
Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 8 Slide 1 System models.
Lecture 13 Revision IMS Systems Analysis and Design.
©Ian Sommerville 2000Software Engineering, 6/e, Chapter 71 System models l Abstract descriptions of systems whose requirements are being analysed.
Fundamentals of Information Systems, Second Edition
Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 8 Slide 1 System models.
1 Lecture 5 Introduction to Software Engineering Overview  What is Software Engineering  Software Engineering Issues  Waterfall Model  Waterfall Model.
Technical Writing Function. The purpose of having guidelines is to make the document more readable. Standard guidelines govern – Format – page layout,
Course Instructor: Aisha Azeem
Foundation Degree IT Project Milestone 2: Design and Project Planning.
The Project AH Computing. Functional Requirements  What the product must do!  Examples attractive welcome screen all options available as clickable.
Introduction to Systems Analysis and Design Trisha Cummings.
Foundation Degree IT Project Methodologies (for reference)
AICT5 – eProject Project Planning for ICT. Process Centre receives Scenario Group Work Scenario on website in October Assessment Window Individual Work.
Review of Unit 1 SBA By Nyoka English. Problem Definition Identifies an organization and gives a brief description of the organization, zeroing in on.
Term 2, 2011 Week 3. CONTENTS The physical design of a network Network diagrams People who develop and support networks Developing a network Supporting.
Section 02Systems Documentation1 02 Systems Documentation And Franchise Colleges By MANSHA NAWAZ.
1 Shawlands Academy Higher Computing Software Development Unit.
Foundation Degree IT Project Milestone 3: Implementation, Testing and Evaluation.
Managing the development and purchase of information systems (Part 1)
Module 4: Systems Development Chapter 13: Investigation and Analysis.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 7 Slide 1 System models l Abstract descriptions of systems whose requirements are being.
Chapter 4 System Models A description of the various models that can be used to specify software systems.
System models Abstract descriptions of systems whose requirements are being analysed Abstract descriptions of systems whose requirements are being analysed.
The Systems Development Methodologies. Objectives  Describe the information Systems Development Life Cycle (SDLC)  Explain prototyping  Explain Rapid.
1 The Software Development Process  Systems analysis  Systems design  Implementation  Testing  Documentation  Evaluation  Maintenance.
©Ian Sommerville 1995/2000 (Modified by Spiros Mancoridis 1999) Software Engineering, 6th edition. Chapter 7 Slide 1 System models l Abstract descriptions.
Chapter 7 System models.
Software Development Process.  You should already know that any computer system is made up of hardware and software.  The term hardware is fairly easy.
System models l Abstract descriptions of systems whose requirements are being analysed.
Pertemuan 19 PEMODELAN SISTEM Matakuliah: D0174/ Pemodelan Sistem dan Simulasi Tahun: Tahun 2009.
Modified by Juan M. Gomez Software Engineering, 6th edition. Chapter 7 Slide 1 Chapter 7 System Models.
Software Engineering, 8th edition Chapter 8 1 Courtesy: ©Ian Somerville 2006 April 06 th, 2009 Lecture # 13 System models.
Sommerville 2004,Mejia-Alvarez 2009Software Engineering, 7th edition. Chapter 8 Slide 1 System models.
Following the submission of your CV and letter of application, the head of Human Resources has invited you to proceed to the second stage of the recruitment.
Intermediate 2 Software Development Process. Software You should already know that any computer system is made up of hardware and software. The term hardware.
Fundamentals of Information Systems, Second Edition 1 Systems Development.
The Software Development Process
Requirements Engineering Lesson 2. Terminologies:  Software Acquisition is where requirement engineering significantly meets business strategy.  Software.
Systems Development Life Cycle
Topic 4 - Database Design Unit 1 – Database Analysis and Design Advanced Higher Information Systems St Kentigern’s Academy.
Module 4: Systems Development Chapter 13: Investigation and Analysis.
Chapter 1 - Introduction
Internet Literacy Evaluating Web Sites. Objective The Student will be able to evaluate internet web sites for accuracy and reliability The Student will.
Yr 7.  Pupils use mathematics as an integral part of classroom activities. They represent their work with objects or pictures and discuss it. They recognise.
Requirements engineering The process of establishing the services that the customer requires from a system and the constraints under which it operates.
1 The Software Development Process ► Systems analysis ► Systems design ► Implementation ► Testing ► Documentation ► Evaluation ► Maintenance.
 To explain why the context of a system should be modelled as part of the RE process  To describe behavioural modelling, data modelling and object modelling.
Requirement Classification Nisa’ul Hafidhoh Teknik Informatika
Software Design and Development Development Methodoligies Computing Science.
A2 Agreement Trial ICT November Key Points from Moderation  Majority of centres applied the assessment criteria successfully  Tasks selected and.
1 Software Requirements Descriptions and specifications of a system.
Getting Ready for the NOCTI test April 30, Study checklist #1 Analyze Programming Problems and Flowchart Solutions Study Checklist.
 System Requirement Specification and System Planning.
Advanced Higher Computing Science
Fundamentals of Information Systems, Sixth Edition
Chapter 5 – Requirements Engineering
Types for Programs and Proofs
System Design Ashima Wadhwa.
The Systems Engineering Context
Foundation Degree IT Project
Unit 09 – LO3 - Be able to Implement and Test Products
Internet Literacy Evaluating Web Sites.
Cambridge TECHNICALS- LEVEL 3
TITLE Business Case YOUR LOGO BUSINESS CASE PRESENTATION 00/00/0000
AICT5 – eProject Project Planning for ICT
Presentation transcript:

Foundation Degree IT Project Milestone 2: Research and Analysis

Objectives Richard Hancock2  Describe what background research is  Describe what implementation specific research is in terms of  What methodologies are and how they affect the project  Technologies  Describe analysis  Describe project requirements in terms of both  Functional requirements  Non-functional requirements  Describe development models 03/12/2015

Background research Richard Hancock3  Relates to the project area  Web design  Networking  Multimedia  Education  Business processes  You need to look at your project area and comment on some of the most important themes or topics that affect that area  Can be very difficult as each project area probably has many topics 03/12/2015

Background research Richard Hancock4  You can look at this from your own perspective relating to your experience in the work environment  What data comes into their area?  How is it processed?  What data leaves?  How do they fit into the rest of the organisation?  Try to document issues that are likely to affect your project in some way  For example: web design  Using the web as a delivery platform  Accessibility/usability  Interaction issues  For most projects you ought to consider what good practices there are relating to your fields  You DO NOT need to document background information relating to the company in this section 03/12/2015

Implementation specific research - Methodologies Richard Hancock5  "the analysis of the principles of methods, rules, and postulates employed by a discipline";  "the systematic study of methods that are, can be, or have been applied within a discipline"; or  "a particular procedure or set of procedures."  Reference: WikipediaWikipedia 1. Research approximately 3 methodologies that you deem useful to your project 2. Choose one and justify your choice 3. You can then apply this methodology to your project by carrying out its activities  The Gantt chart should show evidence of the methodology stages 03/12/2015

Implementation specific research - Technologies Richard Hancock6  Software  Development environments  Programming languages  Operating systems/Servers  Database management systems  Hardware  Network equipment  Server hardware  Machine specification  Other issues  HCI  Security  Web hosting  Look into how the features of technologies are most suitable/relevant to your project 03/12/2015

Analysis Richard Hancock7  It must be clear why your chosen methodology is appropriate to the project  Contrast the advantages and disadvantages of methodologies  What process did you use to make your choice?  If done correctly this should aid in project management  Once a choice is made you need to go deeper into the methodology, make sure you understand the various stages and then follow them  Describe the application of the chosen analysis method, indicating problems arising and how they were overcome  Your project planning (Gantt charts) should be amended to account for the various stages 03/12/2015

Analysis 03/12/2015Richard Hancock8  When analysing the system think about:  Where does data come from?  How does it enter the system?  How is it processed within the system?  What happens to the data after processing?  Does it leave the system? If so how?  Is it retained indefinitely? ***

Analysis models Richard Hancock9  DFDs and supporting descriptions  E-R diagrams  Use cases  Business models  Other appropriate modelling techniques  Be sure to look into the techniques described in your chosen methodology!  Make use of appendices where possible and refer to then in the body of the report if you are running out of your word count currency 03/12/2015

Project requirements Richard Hancock10  The analysis should derive the requirements for the project  Once the analysis is complete you should be in a position to develop a detailed list of requirements of the new system or solution  You can look at similar systems to see how they achieve their objectives for comparison  Functional requirements:  What a system is supposed to accomplish i.e. functions  This is defined by:  Technical details, calculations, data manipulation, processing  Non-functional requirements:  Criteria that specify the operation of a system, NOT the behaviour or function  Performance  Security  Reliability 03/12/2015

Summary Richard Hancock11  Background research  Should relate to your project  Implementation specific research  Methodologies, software, hardware, other resources  Analysis  Use your chosen methodology in order to analyse your project and define requirements  Requirements  Functional – What the system is supposed to do  Non-functional – How the system is supposed to be  Development models  Graphical representations of the current system  Using something like RAD is NOT an excuse for not performing analysis and design!! 03/12/2015

Questions... 03/12/2015Richard Hancock12 ...are there any?

Richard Hancock13 End! 03/12/2015