SA Capstone Requirements and Design Week 10 SYST Winter 2016

Slides:



Advertisements
Similar presentations
2003 Mateusz Żochowski, Marcin Borzymek Software Life Cycle Analysis.
Advertisements

COURSE: COMPUTER PLATFORMS
Enabling Access to Sound Archives through Integration, Enrichment and Retrieval WP1. Project Management.
Monitoring and Control
W5HH Principle As applied to Software Projects
1 The IIPC Web Curator Tool: Steve Knight The National Library of New Zealand Philip Beresford and Arun Persad The British Library An Open Source Solution.
1 Introduction to System Engineering G. Nacouzi ME 155B.
SE 555 Software Requirements & Specification 1 SE 555 Software Requirements & Specification Prototyping.
Systems Development (SD) Presentation Michael Webb IT Director for Medicaid Utah Department of Health UDOH Informatics Brownbag August.
Effort in hours Duration Over Weeks Or Months Inception Launch Web Lifecycle Methodology Maintenance Phases Copyright Wonderlane Studios.
Services Flexible Workstyle and People-Centric IT Windows Accelerate: Deployment Windows 8.1 Proof of Concept (Window 8.1 PoC) will demonstrate how the.
CHAPTER 19 Building Software.
Pricing Changes MSDN subscriptions Stand- alone tool Team collaboration Release management Visual Studio Team Foundation Server Device CAL Visual Studio.
S/W Project Management
Life Cycle Time Line Fall 2000 Spring 2001 Organization Plan.
Introduction to RUP Spring Sharif Univ. of Tech.2 Outlines What is RUP? RUP Phases –Inception –Elaboration –Construction –Transition.
SA Capstone Requirements and Design Week 2 SYST36367 Winter 2013 Instructors: Jerry Kotuba & Joe Varrasso.
University of Sunderland COM369 Unit 8 COM369 Project Monitoring and Control Unit 8.
Statistics Monitor of SPMSII Warrior Team Pu Su Heng Tan Kening Zhang.
Software Engineering Management Lecture 1 The Software Process.
COMP3615,5615 Capstone Projects Week Overview of the semester Website tour – XP and roles – Assessment – note especially the individual mark operating.
1 SA Capstone Requirements and Design Course Introduction SYST36367 Winter 2015.
J. Scott Hawker p. 1Some material © Rational Corp. Rational Unified Process Overview See and use the RUP Browser on lab machines.
RUP Deployment RUP Deployment Workflow
T Iteration Demo Group 1 Project Planning Iteration
SA Capstone Requirements and Design Week 2 SYST36367 Winter 2016
Lecture Notes - Richard Ssembatya1 Information System Project Management Lecture Five By Richard Ssembatya MSc. Cs, BSc CS, CCNA, IT Essentials, ICDL Institute.
What has been accomplished at the end of MSD 1 & 2?
T Project Review MTS [PP] Iteration
Phase-1: Prepare for the Change Why stepping back and preparing for the change is so important to successful adoption: Uniform and effective change adoption.
Stages of Research and Development
CompTIA Server+ Certification (Exam SK0-004)
ADVANCED HOSTING Adrian Newby, CTO.
Process 4 Hours.
Tips to Choose the Best Dedicated Server Hosting Provider
Methodologies and Algorithms
COMM02 Project Monitoring and Control Unit 8
Software Engineering Management
Continuous Delivery- Complete Guide
SA Capstone Requirements and Design Week 2 SYST36367 Winter 2017
Managing the Project Lifecycle
Agile Scrum Management
Introduction to CS Senior Design Project I / II
User Interface Design and Usability Course Introduction
Project Management Processes
PROJECT LIFE CYCLE AND EFFORT ESTIMATION
The Systems Engineering Context
Software Requirements
The Transportation Information Gateway An Open Source Web Platform for Collaboration in the Planning Process AMPO 2017 Annual Meeting Brian ten Siethoff,
Building Information Systems
Level 1 Level 1 – Initial: The software process is characterized as ad hoc and occasionally even chaotic. Few processes are defined, and success depends.
Hyper-V Cloud Proof of Concept Kickoff Meeting <Customer Name>
Graduation Project Kick-off presentation - SET
IT Systems Analysis & Design
SQL Server BI on Windows Azure Virtual Machines
SQL Server OLTP with Microsoft Azure Virtual Machines
Methodologies For Systems Analysis.
Chapter 2 Software Processes
Continuous deployment best practices, methods and tools.
Gathering Systems Requirements
How to keep your Enterprise GIS Project on Track
Project Management Processes
SA Capstone Requirements and Design Week 2 SYST36367 Winter 2018
Introduction to Engineering Design II (IE 202)
Presentation on CAPSTONE PROJECT presented by Cdr MD Masum-ul-Haque, (E), BN ME DEPT MILITARY INSTITUTE of SCIENCE and TECHNOLOGY (MIST)
Weekly Team + Faculty Meetings
Gathering Systems Requirements
Agile software development
NOTICE! These materials are prepared only for the students enrolled in the course Distributed Software Development (DSD) at the Department of Computer.
Presentation transcript:

SA Capstone Requirements and Design Week 10 SYST36367 - Winter 2016

Agenda Review Schedule Today: User Interface Prototyping Proof of Concept Prototyping Sheridan Virtual Machines

User Interface Prototyping User Interface Prototyping is designed to ensure that the customer is comfortable with the User Interface and corresponding workflows before the final product is delivered! It provides many benefits including: Allowing the customer to “Test Drive” the User Interface in order to assess the layout and most importantly the workflows Providing tangible evidence to the customer that you are making progress and are on the right track Reducing the risk that the customer will not like the final GUI or product Getting early feedback from the customer so that many issues can be dealt with earlier. Consequently, as part of your next deliverable (Deliverable 4) you will be delivering a User Interface Prototype that the customer can actually see and use on their own device!

User Interface Prototype Ideally you should develop your User Interface Prototype using the same development tools that you plan on using for the final product You should address any feedback you have received from your customer or Capstone faculty on your User Interface Design in your Deliverable 3 Design Document Remember that you will be required to submit your User Interface Prototype to your customer for review and evaluation

Proof of Concept Prototyping As promoted in the Disciplined Agile Delivery (DAD) Methodology, early in the course you identified areas of risk for your project Now is the time in the course to do some prototyping to address these areas of risk By the end of this semester you should have addressed all of the known risks through prototyping so that you are “cleared for takeoff” in Semester 6! Remember this prototyping is designed to avoid the dreaded “why didn’t you tell me this was a problem before” scenario

Proof of Concept -Definition A proof of concept (POC) or a proof of principle is a realization of a certain method or idea to demonstrate its feasibility, or a demonstration in principle, whose purpose is to verify that some concept or theory has the potential of being used. A proof of concept is usually small and may or may not be complete. Source -Wikipedia

Choosing the Server Platform After choosing your database and development tools you should be in a good position to choose a Server Operating System and Web Server Note that some Database Servers (SQL Server), Web Servers (IIS) and development tools only work on one platform While other Database Servers (MySQL), Web Servers (Apache) and development tools are multi-platform Note that currently Sheridan only supports Windows and Linux Servers for Capstone Virtual Machines

Planning your Development Servers Consider where your development database server(s) and web server(s) will be hosted Try to ensure that all members will have 24x7 access to the development database server(s) and web server(s) Ensure that you have a current backup development server available at all times and that the main development server is not running on only one member’s system

Sheridan Virtual Machines Once you have decided on the Server technologies you require (Database Server, Web Server and Operating System) you should put in a request for a Sheridan Virtual Machine You can use your Sheridan Virtual Machine as a demonstration and development server Do NOT plan on doing your coding and compiling directly on the Sheridan Virtual Machines Do NOT rely exclusively on your Sheridan Virtual Machine as your Development Server. You should have a backup Development Server ready at all times! You will be required to deploy your final system to your Sheridan Virtual Machine in semester 6 for demonstration purposes!

Planning for Deployment Based on the requirements you specified in Deliverable 2 you should choose a suitable permanent site host to deploy your project for your customer Remember that your Sheridan Virtual Machines are NOT designed to be Production Servers and will NOT be available after the conclusion of semester 6!

Exercises In your Capstone Groups discuss: The “Best” Development Tools for your project. This is a very important decision so make sure that you have a thorough discussion and that everyone has a chance to contribute. You do NOT have to decide today! The risk areas of your project which you would like to prototype this semester in order to be comfortable knowing that you have achieved the “Proof of Concept” for your project Your technical requirements for your Sheridan Virtual Machine