Empirical Development of a Mobile Application: UVA- Wise Undergraduate Software Engineering Capstone Project

Size: px
Start display at page:

Download "Empirical Development of a Mobile Application: UVA- Wise Undergraduate Software Engineering Capstone Project"

Transcription

1 Empirical Development of a Mobile Application: UVA- Wise Undergraduate Software Engineering Capstone Project I. Weissberger, S. Showalter, T. Deel, M. Ward, M. Whitt, and A. Qureshi University of Virginia s College at Wise, Wise, VA, United States of America Abstract - Capstone projects allow students to put to use the knowledge they have acquired in the classroom. Projects such as these will serve to reinforce the concepts that may otherwise seem vague or abstract to students when they first encounter them. Capstone projects in software engineering give students the full experience of developing a product from gathering requirements to testing the software to verify those requirements. This paper presents a software engineering capstone project conducted by students at the University of Virginia s College at Wise. Their work and the methodology and tools that they used are recorded with a focus placed on the experience they have gained and additional methods which could be used to enhance the capstone experience. Keywords: Capstone Project, Software Engineering, Software Requirements, Software Design, Requirements Traceability, Project Management 1 Introduction While students pursue degrees in software engineering, they may take several courses that relate to various aspects of the software development life cycle. Courses such as requirements, design, configuration management, project management and testing are all necessary because they teach students about important software engineering concepts that they will need to use in their careers. One of the drawbacks to some of these classes is that they teach concepts in relative isolation to other aspects of software development. In reality, many of these concepts go together. For example, requirements developed in the beginning of a project are traced throughout the course of the development effort to several documents, such as the design document and the testing document. Also, errors made early on during the requirements phase can have repercussions for later phases, which can often include rework to correct the problems. These important concepts might be lost if a student takes a course in requirements and completes a requirements development project but does not need to design, implement, and test those requirements. Capstone projects allow students to connect the different phases of a software engineering development effort by working on a software project over two semesters. Students typically develop a new piece of software, so they are responsible for everything from requirements development to verifying the functionality of the software through formal test procedures. By taking a customer's high level business requirements and completing a product to satisfy those requirements, students can understand how all the different aspects of software engineering connect together. This serves as a complimentary activity to learning theory in the classroom. Often, through practice, students can gain a better grasp of the theory of software engineering rather than solely studying texts. This paper presents work done during the Fall 2012 semester for the software engineering capstone project conducted at the University of Virginia's College at Wise. The software to be developed was intended to be the official application for the university. The Office of Media Relations and Communications was the customer and they had requested a mobile application which would allow users to gain access to information about the school. Currently information about the college is readily available, but it is difficult to find particular pieces of information due to the vast amount of college departments, services, and activities. Android was chosen as a development platform because the department already had mobile phones to support this and it was thought that the Android platform would be the easiest to develop software for. The paper focuses on the development methods the students used to complete the first part of the project (through the beginning of code construction) and could be used to start a template for future software engineering capstone projects. 2 Project Management The capstone project is designed to encompass two semesters. During each of the semesters, the students have to complete different software engineering related tasks. The first semester is designed to make the students complete requirements development activities, produce a design, and to begin coding. The second semester will have the students complete their coding and then verify the software works by running a formal system test. As with any software development effort, there is need for project management activities to track and correct issues to minimize their impact on the project [6]. This is especially true since the students have a fixed schedule that does not allow for very much slack in case the project should start to fall behind. Both semesters include project management activities. The activities during the first semester included creating a schedule complete with

2 milestones, developing a risk mitigation plan, and conducting weekly status meetings. Since the capstone project is supposed to be completed within a given amount of time each semester, the students did not have much leeway in truly estimating how long tasks would take to complete. They had to work being constrained to one semester. However, in creating the schedule, they have learned that it can be a valuable tool to track program status against pre-determined milestones. A risk mitigation plan was developed by the students to think of different scenarios which could happen over the course of the project that would impede their progress. Risks were identified by team members individually and then combined together in a brainstorming session. Each team member came up with a list of risks associated with the project with an estimation based on the probability of the risk occurring and how much of an impact the risk would make on the project. The list of risks were then compiled and discussed to determine final weights associated with those risks. Risks were identified to have two main criteria, probability and impact. Probability was the chance of a risk happening based on a scale of 100. Impact was how fatal the risk could be to the project, on a scale of 10. The risk was then given a score based on the formula as shown in (1). (1) This means that a risk with 30% probability and an impact of 8 had a total score of 24. The scores were then grouped together into general categories ranging from very high to very low. The list of risks identified is presented in Figure 1. Figure 1 Identified Risks Each week, the students would meet to discuss any new risks and to recalculate the total scores of each identified risk as a means of monitoring them. Any risk with a change in total score greater than 10 would be marked and further actions discussed to manage the volatility of the risk. In addition, each type of risk had its own monitoring activities and requirements. For instance, scheduling risks were monitored through a collective schedule of each team member s availability and each member was responsible for informing the team of any changes that needed to be made to their portion of the schedule. The students also developed risk mitigation plans based on the type of risk. Continuing on the previous example, to mitigate schedule risks each team member must keep close tabs on their schedules and inform the other members of the team of changes in their schedule in a timely fashion as well as take steps to ensure flexibility in their scheduling. Status meetings were also held weekly so that students had a chance to discuss their status and any issues that were impeding their progress. Each team member was responsible for presenting a list that included what they had worked on in the past week, their plans of what to work on for the following week, and any issues they had encountered that were holding up progress. This allowed the team to learn about issues and correct them before they became a bigger problem which could greatly affect the project schedule. These items were presented to the group so that each team member was kept up to date on each part of the project. The team understood what was completed, what was being worked on, and when these were supposed to be completed, as well as what hasn't started. With this information, the team could compare the items to the schedule and figure out what needed to be changed to keep the team on track. Items are listed on a percentage complete scale from 0 to 100. This detailed the progress done to the item in order to provide more information for the team. 3 Requirements In order to develop a set of requirements for the project, the students had to perform all four phases of requirements development: elicitation, analysis, specification, and validation [1]. Rarely are all these four phases performed in a one-time linear sequence. Most of the time, the phases are performed in an iterative fashion [2]. This benefits both the software development team and the customer because rework done during the requirements development phase is less costly than rework at the later stages of the software development life cycle. The students started the requirements development phase by having a meeting with the customer to go over what they wanted from the software. At first, they only retrieved very high-level requirements. The initial requirements included having the application retrieve and display the following items: University news feed Campus directory Campus map Directions to the campus University sports feed Alumni information Campus dining information

3 The students met with the Office of Media Relations and Communications several times to elicit requirements. They then scheduled a more detailed interview with the customer in order to formulate an adequate list of requirements. The second meeting with the customer was more informative, and the students were able to start a list of requirements to review with the customer. They took those requirements and considered how they would design the system around them and their feasibility. The students also encouraged the customer to think of more requirements during the time between the second meeting and the third meeting so that they could consider all the requirements before the design phase. To capture the expected behavior of the system from a user s point of view, the students developed use cases to model the interactions between the user and the software. These use cases formed the early part of testing done in parallel with the coding done during the first semester of the capstone project. The use cases would also be used to develop unit tests for the second semester and the test document which would be used during formal system testing. The third meeting reviewed the requirements from the previous meetings and the students also retrieved new ideas and requirements that the customer had thought of since the last meeting. By encouraging the customer to think of any extra requirements early in the requirements gathering phase, the students hoped to avoid any costly additions of extra requirements in the design and coding phases. This was successful because they were able to retrieve a good comprehensive set of requirements. The fourth meeting covered finalizing requirements and reviewing any issues with them. The students and the customer discussed any issues with resources and the feasibility of specific requirements. They also unofficially finalized the list of requirements that were gathered to that point. The final meeting of the requirements gathering phase concerned the formal finalization of the requirements that had been gathered. This included reviewing the entire software requirement specification (SRS) document and noting any missing items. The SRS was based off the IEEE standard [4], and the students had tagged each requirement to provide requirements traceability for other documents to be constructed, such as the software design document and the software test document. The final meeting concluded the requirements phase and the students proceeded to the design phase. During the requirements review, the customer signed off on the requirements, so that they had an understanding that the SRS represented the scope of the project. Over the several meetings that the students had with the customer, the list of the requirements grew. The finalized requirements had all the initial requirements included plus these additional features: Social media site links Student services links Convocation center website access It was beneficial to both parties to agree to baseline the requirements so that would narrow the expectation gap between what the students were developing and what the customer was expecting. 4 Design Once the requirements had been baselined, the students began to create the software design based off the requirements. The students used the IEEE standard [5] to create the software design document (SDD). The SDD contained a requirements traceability matrix so that it was ensured that no requirement was overlooked when making the design. The system was built in three layers: the user interface, logic, and communication. As shown in Figure 2, each of these layers had several corresponding classes that would need to be implemented. Figure 2 Subsystem Packages Due to the unique architecture of the Android operating system, the user interface must be combined with some logic and communication classes. The user interface layer displays all items on screen that the user will need to control, understand, and navigate the application. This layer also holds all user interface items that the system uses. The user interface layer is also a container for the logic layer, and sends input to each of the logic layers functions as they are needed. The logic layer is what holds the methods and classes needed to perform each system action. This layer also holds the data needed to communicate with the user interface layer and the communication layer. The logic layer is also the main level of the application, since it performs the necessary functions. In order to design the interactions between the different layers, the students created sequence diagrams similar to the example shown in Figure 3. The application was designed in a layered architecture due to the need for only three levels of system performance. The user needed to perform an action, the system needed to respond and obtain the data required, which needed a communications level, and then it needed to display that data. The students chose this

4 because it fit the application's needs perfectly and works well with the way the Android OS is designed. The main tool used for the user interface design was Adobe Photoshop CS5.1. The icons for the different pages were designed so that their purpose would be easily recognized. Most icons are original designs with the exception of a few logos. The style of the icons is designed to look like frosted glass buttons which is based on current popular mobile phone applications. Photoshop allowed the students to quickly mock up what a screen would look like in the finished project without having to develop it in an Android application. Based on the functionality required for each screen to operate correctly and fulfill the requirements completely, classes were able to be developed for each screen. The home page contains icons that direct the user to the different pages. The icons are designed so that the user can quickly recognize what type of information which is displayed on the page where the button will direct them. The icons include news, calendar, directory, dining, maps, sports, Moodle, bookstore, the weather channel, and social media. The home page is shown in Figure 4. on the class diagrams that had been developed and that were included in the software design document (SDD). They had also developed a general prototype to establish flow through the application. This first prototype was intended to contain a generic user interface, but function as a final product in the flow of the application. This prototype contained placeholder buttons and icons that were linked to empty screens to ensure that the application worked properly and that each major requirement had a screen that would contain the correct information and functionality. After this prototype passed preliminary tests and was reviewed, it was saved, base lined, and a new iteration was started. This new iteration of the prototype was intended to perform basic tasks and featured the finalized user interface so that it looked and felt like the final version should. As the prototypes were developed, each time a method was changed or added, a unit test was performed to ensure that the system worked correctly and was stable. The students approached the project with the philosophy of extensively testing each method to ensure that every part of the application worked on the most basic level. Figure 3 Sequence Diagram The bottom of the home page will also contain an information and alert crawler. Text will scroll across the bottom of the screen letting the user know the important messages without having to click any icons. Most icons will direct the user to a filter page to filter out the information that is displayed on each page. The pages that will have a filter page include the news, directory, dining, maps, sports, and alumni icons. The directory, news, and sports pages will contain filters as well as a search option that will be at the top of the page. 5 Code Construction The students began the coding phase by establishing coding standards. They proceeded to code the project based Figure 4 Application Home Screen 6 Configuration Management A configuration management process was established to maintain the software and all supporting documents and information for the project. The students used Git [3], an open source tool, to manage changes to files and documentation for the project. They also devised a change control process, as shown in Figure 5, in order to evaluate change requests, whether they came from the client or a team member. Change

5 requests were evaluated by the team, which consisted of discussing alternatives to the change and whether or not it was necessary. If deemed necessary and the best way to make the change, the change was implemented into the system. From there, the change was validated to ensure it was the right way to correct or improve the previous implementation. If the change was validated it would then be incorporated into the system. Change management was essential in deciding what the schedule could handle as new requirements were added to the system. Early on the decision was made to incorporate a reporting and analysis section to the system, and through the change management process the students were able to evaluate the functionalities worth and determine what it provided the system and customer. 9 References [1] Introduction to Software Engineering Body of Knowledge, Last accessed on March 8, [2] Karl Wiegers, Software Requirements 2 nd Edition, Microsoft Press, 2009 [3] Git, Last accessed on March 8, 2013 [4] IEEE Std , IEEE Recommended Practice for Software Requirements Specifications, IEEE, [5] IEEE Std , IEEE Recommended Practice for Software Design Descriptions, IEEE, [6] Introduction to the Software Engineering Body of Knowledge, Last accessed on March 8, Conclusions Figure 5 Change Control Process This paper presented the first half of a senior capstone project that focused primarily on gathering requirements and producing a suitable design. The code construction commenced in the first semester of the project, but will not be completed until the following semester. The students gained a great deal of experience by having to develop a product from the beginning by using the concepts they have learned in taking software engineering courses. Having a consistent process in place benefited the students by informing them what was expected. It would be beneficial for a university teaching software engineering to have a defined process and document templates that capstone projects could use. This could be similar to an organization developing its own software process to make it more consistent between various projects in the organization. The process may then be modified depending on the project type. 8 Acknowledgements The authors would like to express a sincere appreciation to The Office of Media Relations and Communications at the University of Virginia s College at Wise for support of the capstone project presented in this paper.

Student Registration Online Classes

Student Registration Online Classes Student Registration Online Classes Purpose: This document walks returning or accepted students through the process of registering for online classes at Moody Bible Institute. Contents 1 The mymoody Portal

More information

Student Registration Moody Theological Seminary

Student Registration Moody Theological Seminary Student Registration Moody Theological Seminary Purpose: This document walks students through the process of registering for classes at Moody Theological Seminary. It covers Chicago campus ( Main Campus

More information

Appendix 2-A. Application and System Development Requirements

Appendix 2-A. Application and System Development Requirements Appendix 2-A. Application and System Development Requirements Introduction AHRQ has set up a Distributed Systems Engineering Lab (DSEL) to support all internal development efforts and provide a facility

More information

Listening to the Customer s Voice 1

Listening to the Customer s Voice 1 Listening to the Customer s Voice 1 Karl E. Wiegers Process Impact 716-377-5110 www.processimpact.com Perhaps the greatest challenge facing the software developer is sharing the vision of the final product

More information

Administrator s Guide

Administrator s Guide SEO Toolkit 1.3.0 for Sitecore CMS 6.5 Administrator s Guide Rev: 2011-06-07 SEO Toolkit 1.3.0 for Sitecore CMS 6.5 Administrator s Guide How to use the Search Engine Optimization Toolkit to optimize your

More information

Swirl. Multiplayer Gaming Simplified. CS4512 Systems Analysis and Design. Assignment 1 2010. Marque Browne 0814547. Manuel Honegger - 0837997

Swirl. Multiplayer Gaming Simplified. CS4512 Systems Analysis and Design. Assignment 1 2010. Marque Browne 0814547. Manuel Honegger - 0837997 1 Swirl Multiplayer Gaming Simplified CS4512 Systems Analysis and Design Assignment 1 2010 Marque Browne 0814547 Manuel Honegger - 0837997 Kieran O' Brien 0866946 2 BLANK MARKING SCHEME 3 TABLE OF CONTENTS

More information

Module A2 Item Activities, Gantt Chart and Utilization Sheet. A2.1 Project item activities A2.2 Gantt chart A2.3 Utilization sheet

Module A2 Item Activities, Gantt Chart and Utilization Sheet. A2.1 Project item activities A2.2 Gantt chart A2.3 Utilization sheet Module A2 Item Activities, Gantt Chart and Utilization Sheet A2.1 Project item activities A2.2 Gantt chart A2.3 Utilization sheet 1 Assistance PSA: Advanced Functionalities Welcome to the Advanced Functionalities

More information

A system is a set of integrated components interacting with each other to serve a common purpose.

A system is a set of integrated components interacting with each other to serve a common purpose. SYSTEM DEVELOPMENT AND THE WATERFALL MODEL What is a System? (Ch. 18) A system is a set of integrated components interacting with each other to serve a common purpose. A computer-based system is a system

More information

(Refer Slide Time: 01:52)

(Refer Slide Time: 01:52) Software Engineering Prof. N. L. Sarda Computer Science & Engineering Indian Institute of Technology, Bombay Lecture - 2 Introduction to Software Engineering Challenges, Process Models etc (Part 2) This

More information

Improve Your Process With Online Good Practices 1

Improve Your Process With Online Good Practices 1 Improve Your Process With Online Good Practices 1 Karl Wiegers Process Impact www.processimpact.com Most software developers are allergic to paper. As organizations improve their software development and

More information

User experience prototype requirements PROJECT MANAGEMENT PLAN

User experience prototype requirements PROJECT MANAGEMENT PLAN Tallinn University Institute of Informatics User experience prototype requirements PROJECT MANAGEMENT PLAN Authors Roger Puks Erkki Saarnit Ekaterina Shafeeva Maria Angelica Medina Angarita Lecturer Peeter

More information

SMS/Text Message Solution User Guide. How to send bulk SMS messages. Copyright 2013 xrm Consultancy Limited

SMS/Text Message Solution User Guide. How to send bulk SMS messages. Copyright 2013 xrm Consultancy Limited SMS/Text Message Solution User Guide How to send bulk SMS messages Contents Contents... 2 Introduction... 3 Pre-requisites... 3 North52 Formula Manager... 3 Sending bulk SMS messages... 4 1. Set up workflow...

More information

JOURNAL OF OBJECT TECHNOLOGY

JOURNAL OF OBJECT TECHNOLOGY JOURNAL OF OBJECT TECHNOLOGY Online at www.jot.fm. Published by ETH Zurich, Chair of Software Engineering JOT, 2006 Vol. 5. No. 8, November-December 2006 Requirements Engineering Tasks Donald Firesmith,

More information

A quick guide to. Social Media

A quick guide to. Social Media A quick guide to Social Media In this guide... Learn how to integrate your email marketing with social media to get the most out of online buzz! Use Twitter and Facebook integrations to enable readers

More information

Software Requirements, Third Edition

Software Requirements, Third Edition j Microsoft Software Requirements, Third Edition Karl Wiegers and Joy Beatty Contents Introduction Acknowledgments xxv xxxi PART I SOFTWARE REQUIREMENTS: WHAT, WHY, AND WHO Chapter 1 The essential software

More information

Practice Overview. REQUIREMENTS DEFINITION Issue Date: Revision Date:

Practice Overview. REQUIREMENTS DEFINITION Issue Date: <mm/dd/yyyy> Revision Date: <mm/dd/yyyy> DEPARTMENT OF HEALTH AND HUMAN SERVICES ENTERPRISE PERFORMANCE LIFE CYCLE FRAMEWORK PRACTIICES GUIIDE REQUIREMENTS DEFINITION Issue Date: Revision Date: Document

More information

A Project Based Approach for Teaching System Analysis, Design, and Implementation Courses

A Project Based Approach for Teaching System Analysis, Design, and Implementation Courses A Project Based Approach for Teaching System Analysis, Design, and Implementation Courses Nabil A. Yousif 1 and Masoud Naghedolfeizi 2 Abstract-In curricula of Computer Information Systems at Fort Valley

More information

ThirtySix Software WRITE ONCE. APPROVE ONCE. USE EVERYWHERE. www.thirtysix.net SMARTDOCS 2014.1 SHAREPOINT CONFIGURATION GUIDE THIRTYSIX SOFTWARE

ThirtySix Software WRITE ONCE. APPROVE ONCE. USE EVERYWHERE. www.thirtysix.net SMARTDOCS 2014.1 SHAREPOINT CONFIGURATION GUIDE THIRTYSIX SOFTWARE ThirtySix Software WRITE ONCE. APPROVE ONCE. USE EVERYWHERE. www.thirtysix.net SMARTDOCS 2014.1 SHAREPOINT CONFIGURATION GUIDE THIRTYSIX SOFTWARE UPDATED MAY 2014 Table of Contents Table of Contents...

More information

Department of Cultural Resources MOBILE APPS NORTH CAROLINA AGENCIES GOING MOBILE

Department of Cultural Resources MOBILE APPS NORTH CAROLINA AGENCIES GOING MOBILE Department of Cultural Resources MOBILE APPS NORTH CAROLINA AGENCIES GOING MOBILE CATEGORY: Information Technology Communications STATE: North Carolina EXECUTIVE SUMMARY The increasing demand for North

More information

Project Management Tools

Project Management Tools Project Management Tools 1 Name: Subject: Professor: Date: Project Management Tools Project Management Tools 2 1. Introduction Project Management is a method of organizing and managing resources in strategic

More information

SOFTWARE ENGINEERING INTERVIEW QUESTIONS

SOFTWARE ENGINEERING INTERVIEW QUESTIONS SOFTWARE ENGINEERING INTERVIEW QUESTIONS http://www.tutorialspoint.com/software_engineering/software_engineering_interview_questions.htm Copyright tutorialspoint.com Dear readers, these Software Engineering

More information

Time Monitoring Tool Software Development Plan. Version <1.1>

Time Monitoring Tool Software Development Plan. Version <1.1> Time Monitoring Tool Software Development Plan Version Revision History Date Version Description Author 10/01/01 1.0 First Draft Sabrina Laflamme 12/01/01 1.1 Completion of Document John Lemon Page

More information

Modeling the Mobile Application Development Lifecycle

Modeling the Mobile Application Development Lifecycle , March 12-14, 2014, Hong Kong Modeling the Mobile Application Development Lifecycle Tejas Vithani, Member, IAENG and Anand Kumar Abstract Software Development Lifecycle is crucial in Desktop or web application

More information

Architecture Centric Development in Software Product Lines

Architecture Centric Development in Software Product Lines Architecture Centric Development in Software Product Lines Aurangzeb Khan DCE, College of E & ME National University of Science and Technology (NUST), Pakistan Farooque Azam DCE, College of E & ME National

More information

Software Design Document (SDD) Template

Software Design Document (SDD) Template (SDD) Template Software design is a process by which the software requirements are translated into a representation of software components, interfaces, and data necessary for the implementation phase.

More information

Microsoft Outlook 2010

Microsoft Outlook 2010 Microsoft Outlook 2010 Prepared by Computing Services at the Eastman School of Music July 2010 Contents Microsoft Office Interface... 4 File Ribbon Tab... 5 Microsoft Office Quick Access Toolbar... 6 Appearance

More information

Outlook Web App (Online)... 3 Outlook 2013 (Desktop)... 16 Apple Mail Mobile Devices... 33 Android... 33 iphone... 40

Outlook Web App (Online)... 3 Outlook 2013 (Desktop)... 16 Apple Mail Mobile Devices... 33 Android... 33 iphone... 40 Webmail Tutorials Page 2 Table of Contents Outlook Web App (Online)... 3 How do I send an email?... 3 How do I create rules to manage my email?... 3 How do I forward email to my personal account?... 4

More information

Title: SharePoint Advanced Training

Title: SharePoint Advanced Training 416 Agriculture Hall Michigan State University 517-355- 3776 http://support.anr.msu.edu support@anr.msu.edu Title: SharePoint Advanced Training Document No. - 106 Revision Date - 10/2013 Revision No. -

More information

Microsoft Dynamics GP. Manufacturing Planning Functions

Microsoft Dynamics GP. Manufacturing Planning Functions Microsoft Dynamics GP Manufacturing Planning Functions Copyright Copyright 2007 Microsoft Corporation. All rights reserved. Complying with all applicable copyright laws is the responsibility of the user.

More information

Frequently Asked Questions PowerSchool Student Information System

Frequently Asked Questions PowerSchool Student Information System PowerSchool Student Information System Document Properties Frequently Asked Questions Copyright Owner 2003 Apple Computer, Inc. All rights reserved. This document is the property of Apple Computer, Inc.

More information

CDC UNIFIED PROCESS PRACTICES GUIDE

CDC UNIFIED PROCESS PRACTICES GUIDE Document Purpose The purpose of this document is to provide guidance on the practice of Requirements Definition and to describe the practice overview, requirements, best practices, activities, and key

More information

Requirements Management Best Practices

Requirements Management Best Practices Requirements Management Best Practices Sponsored by: Karl Wiegers Principal Consultant, Process Impact www.processimpact.com Sponsor: RequirementOne Free 30 day trial Sign up by 31 st May and benefit from

More information

WIDA Assessment Management System (WIDA AMS) User Guide, Part 2

WIDA Assessment Management System (WIDA AMS) User Guide, Part 2 WIDA Assessment Management System (WIDA AMS) User Guide, Part 2 Data Recognition Corporation (DRC) 13490 Bass Lake Road Maple Grove, MN 55311 Direct: 1-855-787-9615 https://wida-ams.us Revision Date: September

More information

Chapter 1 - From Beginning to End: An Overview of Systems Analysis and Design Lecture Notes

Chapter 1 - From Beginning to End: An Overview of Systems Analysis and Design Lecture Notes Systems Analysis and Design in a Changing World, sixth edition 1-1 Chapter 1 - From Beginning to End: An Overview of Systems Analysis and Design Lecture Notes Table of Contents Chapter Overview Learning

More information

Microsoft Project 2007 Level 2: Working with Resources and Managing a Project

Microsoft Project 2007 Level 2: Working with Resources and Managing a Project Microsoft Project 2007 Level 2: Working with Resources and Managing a Project By Robin Peers Robin Peers, 2008 ABOUT THIS CLASS In Microsoft Project 2007 Level 1: Creating Project Tasks, the focus was

More information

Administrator's Guide

Administrator's Guide Search Engine Optimization Module Administrator's Guide Installation and configuration advice for administrators and developers Sitecore Corporation Table of Contents Chapter 1 Installation 3 Chapter 2

More information

AN INTEGRATED APPROACH TO TEACHING SPREADSHEET SKILLS. Mindell Reiss Nitkin, Simmons College. Abstract

AN INTEGRATED APPROACH TO TEACHING SPREADSHEET SKILLS. Mindell Reiss Nitkin, Simmons College. Abstract AN INTEGRATED APPROACH TO TEACHING SPREADSHEET SKILLS Mindell Reiss Nitkin, Simmons College Abstract As teachers in management courses we face the question of how to insure that our students acquire the

More information

Microsoft Project Activity

Microsoft Project Activity Microsoft Project Activity Purpose: The goal of this activity is to lead you through the most important data entry and formatting activities in MS Project and to provide you with the fundamental knowledge

More information

TenStep Project Management Process Summary

TenStep Project Management Process Summary TenStep Project Management Process Summary Project management refers to the definition and planning, and then the subsequent management, control, and conclusion of a project. It is important to recognize

More information

Student User Guide Index:

Student User Guide Index: Student User Guide Index: Your HireTigers Home Page P. 2 Completing Your Profile P. 3 Searching for Jobs P. 4 Document Library P. 5 Adding Documents P. 6 Opt In Resume P. 7 Resources Career Explorer P.

More information

11 Tips to make the requirements definition process more effective and results more usable

11 Tips to make the requirements definition process more effective and results more usable 1 11 Tips to make the s definition process more effective and results more usable This article discusses what I believe are the key techniques for making s definition process repeatable from project to

More information

Adobe Flash Catalyst CS5.5

Adobe Flash Catalyst CS5.5 Adobe Flash Catalyst CS5.5 Create expressive interfaces and interactive content without writing code Use a new efficient workflow to collaborate intelligently and roundtrip files with developers who use

More information

Montana Department of Transportation Information Services Division. System Development Life Cycle (SDLC) Guide

Montana Department of Transportation Information Services Division. System Development Life Cycle (SDLC) Guide Montana Department of Transportation Information Services Division System Development Life Cycle (SDLC) Guide Version 2 August 2, 2007 \mdt_sdlc_process\mdt_sdlc_v02.doc Table of Contents 1 Business Analysis...3

More information

An Integrated Quality Assurance Framework for Specifying Business Information Systems

An Integrated Quality Assurance Framework for Specifying Business Information Systems An Integrated Quality Assurance Framework for Specifying Business Information Systems Frank Salger 1, Stefan Sauer 2, Gregor Engels 1,2 1 Capgemini sd&m AG, Carl-Wery-Str. 42, D-81739 München, Germany

More information

Siemens Industry Online Support Searching and filtering - keyword search. Search Alternative 1. Keyword search

Siemens Industry Online Support Searching and filtering - keyword search. Search Alternative 1. Keyword search Searching and filtering - keyword search Search Alternative 1 Keyword search Enter one or more keywords in the search box on the home page. For example: - Contactor 5.5 kw - S7 1200 - Frequency converter

More information

Microsoft Dynamics GP 2010

Microsoft Dynamics GP 2010 Microsoft Dynamics GP 2010 Workflow Administrator s Guide March 30, 2010 Copyright Copyright 2010 Microsoft. All rights reserved. Limitation of liability This document is provided as-is. Information and

More information

Software Project Management Plan (SPMP)

Software Project Management Plan (SPMP) Software Project Management Plan (SPMP) The basic template to be used is derived from IEEE Std 1058-1998, IEEE Standard for Software Project Management Plans. The following is a template for the SPMP.

More information

3C05: Unified Software Development Process

3C05: Unified Software Development Process 3C05: Unified Software Development Process 1 Unit 5: Unified Software Development Process Objectives: Introduce the main concepts of iterative and incremental development Discuss the main USDP phases 2

More information

Table of Contents Author s Preface... 3 Table of Contents... 5 Introduction... 6 Step 1: Define Activities... 7 Identify deliverables and decompose

Table of Contents Author s Preface... 3 Table of Contents... 5 Introduction... 6 Step 1: Define Activities... 7 Identify deliverables and decompose 1 2 Author s Preface The Medialogist s Guide to Project Time Management is developed in compliance with the 9 th semester Medialogy report The Medialogist s Guide to Project Time Management Introducing

More information

Kentico CMS 7.0 Intranet Administrator's Guide

Kentico CMS 7.0 Intranet Administrator's Guide Kentico CMS 7.0 Intranet Administrator's Guide 2 Kentico CMS 7.0 Intranet Administrator's Guide Table of Contents Introduction 5... 5 About this guide Getting started 7... 7 Installation... 11 Accessing

More information

Basic Unified Process: A Process for Small and Agile Projects

Basic Unified Process: A Process for Small and Agile Projects Basic Unified Process: A Process for Small and Agile Projects Ricardo Balduino - Rational Unified Process Content Developer, IBM Introduction Small projects have different process needs than larger projects.

More information

WELCOME TO CORNERSTONE ONDEMAND LMS FUNCTIONALITY TRAINING

WELCOME TO CORNERSTONE ONDEMAND LMS FUNCTIONALITY TRAINING Slide 1 WELCOME TO CORNERSTONE ONDEMAND LMS FUNCTIONALITY TRAINING Curriculum Management / Mandatory Training Slide 2 Objectives: At the end of this session, you should be able to: Create a curriculum

More information

System requirements 2. Overview 3. My profile 5. System settings 6. Student access 10. Setting up 11. Creating classes 11

System requirements 2. Overview 3. My profile 5. System settings 6. Student access 10. Setting up 11. Creating classes 11 Table of contents Login page System requirements 2 Landing page Overview 3 Adjusting My profile and System settings My profile 5 System settings 6 Student access 10 Management Setting up 11 Creating classes

More information

How to Build a SharePoint Website

How to Build a SharePoint Website How to Build a SharePoint Website Beginners Guide to SharePoint Overview: 1. Introduction 2. Access your SharePoint Site 3. Edit Your Home Page 4. Working With Text 5. Inserting Pictures 6. Making Tables

More information

What is a Search Engine?

What is a Search Engine? What is a Search Engine? Hi. It s me, Sarah and I m here to tell you about finding things on the Internet. The Internet brings together information from all over the world, which is a lot of information.

More information

TUTORIAL: Marketing Automation Gold-Vision 7

TUTORIAL: Marketing Automation Gold-Vision 7 Marketing Automation What is a Marketing Automation? Campaign Automation Automated Connect Campaigns Automated Telephone Campaigns Automated Lead Call Back Campaigns Phone Campaigns with Activities Creating

More information

Microsoft Dynamics GP Release. Workflow Administrator s Guide

Microsoft Dynamics GP Release. Workflow Administrator s Guide Microsoft Dynamics GP Release Workflow Administrator s Guide December 10, 2012 Copyright Copyright 2012 Microsoft. All rights reserved. Limitation of liability This document is provided as-is. Information

More information

The What, Why, Who, When and How of Software Requirements

The What, Why, Who, When and How of Software Requirements SUMMARY The What, Why, Who, When and How of Software Requirements Linda Westfall President The Westfall Team 3000 Custer Road, Suite 270, PMB 101 Plano, TX 75075 lwestfall@westfallteam.com www.westfallteam.com

More information

Search help. More on Office.com: images templates. Here are some basic tasks that you can do in Microsoft Excel 2010.

Search help. More on Office.com: images templates. Here are some basic tasks that you can do in Microsoft Excel 2010. Page 1 of 8 Excel 2010 Home > Excel 2010 Help and How-to > Getting started with Excel Search help More on Office.com: images templates Basic tasks in Excel 2010 Here are some basic tasks that you can do

More information

Using the BWSD Help Desk Website

Using the BWSD Help Desk Website Accessing the Help Desk Website Using the BWSD Help Desk Website Open your web browser and go to http://helpdesk.bwschools.net:8080/ The Help Desk login screen will be displayed. 1. You should not have

More information

Module A2 Item Activities, Gantt Chart and Utilization Sheet

Module A2 Item Activities, Gantt Chart and Utilization Sheet Module A2 Item Activities, Gantt Chart and Utilization Sheet A2.1 Project item activities A2.2 Gantt chart A2.3 Utilization sheet 1 Module 1. Project item activities, Gantt Chart & Utilization Sheet Contents...

More information

Xerox econcierge Account Setup Guide

Xerox econcierge Account Setup Guide Xerox econcierge Account Setup Guide Xerox econcierge Account Setup Guide The free Xerox econcierge service provides the quickest, easiest way for your customers to order printer supplies for all their

More information

Software Development Life Cycle

Software Development Life Cycle 4 Software Development Life Cycle M MAJOR A J O R T TOPICSO P I C S Objectives... 52 Pre-Test Questions... 52 Introduction... 53 Software Development Life Cycle Model... 53 Waterfall Life Cycle Model...

More information

Advanced Outlook Tutorials

Advanced Outlook Tutorials Advanced Outlook Tutorials Filtering: Create a filter to send email directly to a specific folder from a certain sender: 1. Right click on the sender s email. 2. Choose Rules. 3. Click on Create Rule.

More information

my.uic - Portal Features and Customization

my.uic - Portal Features and Customization my.uic - Portal Features and Customization What is my.uic? my.uic is the University of Illinois web portal. It unifies a vast amount of information into a series of easily navigable pages. From admissions

More information

Screen Design : Navigation, Windows, Controls, Text,

Screen Design : Navigation, Windows, Controls, Text, Overview Introduction Fundamentals of GUIs - methods - Some examples Screen : Navigation, Windows, Controls, Text, Evaluating GUI Performance 1 Fundamentals of GUI What kind of application? - Simple or

More information

1... Overview of Project Portfolio Management with SAP... 15 1.1... Requirements Scenario for Project Portfolio Management... 15...

1... Overview of Project Portfolio Management with SAP... 15 1.1... Requirements Scenario for Project Portfolio Management... 15... 1... Overview of Project Portfolio Management with SAP... 15 1.1... Requirements Scenario for Project Portfolio Management... 15... Project Initialization 1... 15... Project Planning 2... 17... Resource

More information

Mail Merges, Labels and Email Message Merges in Word 2007 Contents

Mail Merges, Labels and Email Message Merges in Word 2007 Contents Mail Merges, Labels and Email Message Merges in Word 2007 Contents Introduction to Mail Merges... 2 Mail Merges Using the Mail Merge Wizard... 3 Creating the Main Document... 3 Selecting the Data Source...

More information

Content Manager User Guide Information Technology Web Services

Content Manager User Guide Information Technology Web Services Content Manager User Guide Information Technology Web Services The login information in this guide is for training purposes only in a test environment. The login information will change and be redistributed

More information

Netspective Software Development Process

Netspective Software Development Process Netspective Software Development Process The process is a tailored evolutionary prototyping-based process with hints of agile development. Evolutionary prototyping is a form of software system creation

More information

THE CAREER COUNSELOR S GUIDE TO LINKEDIN

THE CAREER COUNSELOR S GUIDE TO LINKEDIN THE CAREER COUNSELOR S GUIDE TO LINKEDIN by Kevin Grubb National Association of Colleges and Employers 62 Highland Avenue Bethlehem, PA 18017 Phone: 610.868.1421 www.naceweb.org Copyright 2013 by the National

More information

Using the Student Center: Understanding My Advisement Report

Using the Student Center: Understanding My Advisement Report Using the Student Center: Understanding My Advisement Report The Student Center is a self service page that provides students an entry to the HUB. Along with MyUB, it provides navigation to tools and information

More information

Team A Final Report. Cal Poly Knowledge Base Project

Team A Final Report. Cal Poly Knowledge Base Project Team A Final Report Cal Poly Knowledge Base Project PROBLEM DESCRIPTION The Genius Bar is a technical helpdesk that will be located in the Library Learning Commons. We anticipate that this helpdesk will

More information

Lecture 10 CS5702. Requirements Engineering. Managing change optimising Value - A bit more about Agile RE. Requirements Engineering.

Lecture 10 CS5702. Requirements Engineering. Managing change optimising Value - A bit more about Agile RE. Requirements Engineering. Requirements Engineering Overview Lecture 10 CS5702 Requirements Engineering Semester 1 2009/10 Professor Kevin Ryan 1. Introduction (Week 1) 2. Elicitation of requirements (2 & 3) 3. Standards, Templates

More information

Retrieving Business Applications using Open Web API s Web Mining Executive Dashboard Application Case Study

Retrieving Business Applications using Open Web API s Web Mining Executive Dashboard Application Case Study ISSN:0975-9646 A.V.Krishna Prasad et al. / (IJCSIT) International Journal of Computer Science and Information Technologies, Vol. 1 (3), 2010, 198-202 Retrieving Business Applications using Open Web API

More information

Schools Remote Access Server

Schools Remote Access Server Schools Remote Access Server This system is for school use only. Not for personal or private file use. Please observe all of the school district IT rules. 6076 State Farm Rd., Guilderland, NY 12084 Phone:

More information

FPT UNIVERSITY. Capstone Project

FPT UNIVERSITY. Capstone Project MINISTRY OF EDUCATION AND TRAINING FPT UNIVERSITY Capstone Project Online Event Organizing Company Management System Group Group Members Đoàn Minh Thiện 60130 Nguyễn Thanh Thống 60561 Mai Hoàng Trí Anh

More information

Using the Jive for ios App

Using the Jive for ios App Using the Jive for ios App TOC 2 Contents App Overview...3 System Requirements... 4 Release Notes...5 Which Version Am I Using?... 6 Connecting to Your Community... 11 Getting Started...12 Using Your Inbox...13

More information

Usability Issues in Web Site Design

Usability Issues in Web Site Design Version 3, April 98 (available from http://www.npl.co.uk/npl/sections/us and in Proceedings of UPA 98) Usability Issues in Web Site Design Nigel Bevan National Physical Laboratory, Usability Services,

More information

The new Moodle landing page Introducing the course filter Moodle Help Materials

The new Moodle landing page Introducing the course filter Moodle Help Materials THE UNIVERSITY OF GREENWICH The new Moodle landing page Introducing the course filter Moodle Help Materials Compiled by the Web Services Team webservices@gre.ac.uk Last updated: 06/09/2012 Filtering courses

More information

Overview of the System Engineering Process. Prepared by

Overview of the System Engineering Process. Prepared by Overview of the System Engineering Process Prepared by Ed Ryen, PE Maintenance ITS March 2008 Introduction This document provides a high level look at the Systems Engineering Process for ITS projects.

More information

Software Engineering Prof. N.L. Sarda Computer Science & Engineering Indian Institute of Technology, Bombay Lecture-4 Overview of Phases (Part - II)

Software Engineering Prof. N.L. Sarda Computer Science & Engineering Indian Institute of Technology, Bombay Lecture-4 Overview of Phases (Part - II) Software Engineering Prof. N.L. Sarda Computer Science & Engineering Indian Institute of Technology, Bombay Lecture-4 Overview of Phases (Part - II) We studied the problem definition phase, with which

More information

Social Media for Education on Mobile: A Case Study of College of Arts, Media and Technology, Thailand

Social Media for Education on Mobile: A Case Study of College of Arts, Media and Technology, Thailand Social Media for Education on Mobile: A Case Study of College of Arts, Media and Technology, Thailand Jenjira Jaimunk and Pradorn Sureephong Abstract The purpose of this work is investigation on utilizing

More information

CWT Traveler Assistant

CWT Traveler Assistant CWT Traveler Assistant Important Note: This document contains suggested answers to commonly asked questions. If these answers do not apply to your situation, or if you need further assistance, please contact

More information

4.1 Domain Analysis. Object-Oriented Software Engineering Practical Software Development using UML and Java

4.1 Domain Analysis. Object-Oriented Software Engineering Practical Software Development using UML and Java 4.1 Domain Analysis Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 4: Developing The process by which a software engineer learns about the domain to better

More information

PSA 2015 Step by Step Guide is published by Assistance Software. All rights reserved. No part of this publication may be Projects reproduced.

PSA 2015 Step by Step Guide is published by Assistance Software. All rights reserved. No part of this publication may be Projects reproduced. Step by Step Guide PSA 2015 Module 4 4.1 BAFPA Methodology 4.2 & Budget 4.3 Project sales forecast 4.4 Project & Resource planning 4.5 Utilization Sheet 4.6 CRM Appointments and Group calendar 4.7 Programs

More information

Unleash the Power of e-learning

Unleash the Power of e-learning Unleash the Power of e-learning Version 1.5 November 2011 Edition 2002-2011 Page2 Table of Contents ADMINISTRATOR MENU... 3 USER ACCOUNTS... 4 CREATING USER ACCOUNTS... 4 MODIFYING USER ACCOUNTS... 7 DELETING

More information

SysAidTM ITIL Package Guide. Change Management, Problem Management and CMDB

SysAidTM ITIL Package Guide. Change Management, Problem Management and CMDB SysAidTM ITIL Package Guide Change Management, Problem Management and CMDB Document Updated: 10 November 2009 Introduction 2 First Chapter: Change Management 5 Chapter 2: Problem Management 33 Chapter

More information

ALEKS. Custom Reports

ALEKS. Custom Reports ALEKS Custom Reports ALEKS administrators and instructors can create custom reports in order to meet advanced reporting needs at various levels. Administrators and instructors can select data from existing

More information

15 Principles of Project Management Success

15 Principles of Project Management Success 15 Principles of Project Management Success Project management knowledge, tools and processes are not enough to make your project succeed. You need to get away from your desk and get your hands dirty.

More information

Business 360 Online - Product concepts and features

Business 360 Online - Product concepts and features Business 360 Online - Product concepts and features Version November 2014 Business 360 Online from Software Innovation is a cloud-based tool for information management. It helps you to work smarter with

More information

Using Mail Merge to Create Form Letters and Labels

Using Mail Merge to Create Form Letters and Labels Using Mail Merge to Create Form Letters and Labels 1. Open the word document on your floppy: Practice letter 2. Go to Tools > Mail Merge. The Mail Merger Helper appears. We are going to create form letters,

More information

Silect Software s MP Author

Silect Software s MP Author Silect MP Author for Microsoft System Center Operations Manager Silect Software s MP Author User Guide September 2, 2015 Disclaimer The information in this document is furnished for informational use only,

More information

{COMPANY NAME} website proposal

{COMPANY NAME} website proposal {COMPANY NAME} website proposal MONTH YEAR Prepared By: The Brand Affect, LLC Prepared For: [Prospective Client] INTRODUCTION Thank you for the opportunity to submit a proposal for the design of the {COMPANY

More information

REVIEW ON THE EFFECTIVENESS OF AGILE UNIFIED PROCESS IN SOFTWARE DEVELOPMENT WITH VAGUE SYSTEM REQUIREMENTS

REVIEW ON THE EFFECTIVENESS OF AGILE UNIFIED PROCESS IN SOFTWARE DEVELOPMENT WITH VAGUE SYSTEM REQUIREMENTS REVIEW ON THE EFFECTIVENESS OF AGILE UNIFIED PROCESS IN SOFTWARE DEVELOPMENT WITH VAGUE SYSTEM REQUIREMENTS Lisana Universitas Surabaya (UBAYA), Raya Kalirungkut, Surabaya, Indonesia E-Mail: lisana@ubaya.ac.id

More information

Ad Astra 7.5 Guest Portal Overview and Tutorial

Ad Astra 7.5 Guest Portal Overview and Tutorial Ad Astra 7.5 Guest Portal Overview and Tutorial Overview Astra Schedule is the software utilized by the Office of the Registrar, Classroom Scheduling, for assignment of General Assignment Classrooms (GAC)

More information

Requirements Definition and Management Processes

Requirements Definition and Management Processes Software Engineering G22.2440-001 Session 1 Sub-Topic 1 Requirements Definition & Management Processes and Tools Dr. Jean-Claude Franchitti New York University Computer Science Department Courant Institute

More information

Microsoft Dynamics NAV Connector. User Guide

Microsoft Dynamics NAV Connector. User Guide Microsoft Dynamics NAV Connector User Guide Microsoft Dynamics NAV Connector, version 1.0 Copyright Bottomline Technologies, Inc. 2008. All Rights Reserved Information in this document is subject to change

More information

Requirements Management Database

Requirements Management Database Project Whitepaper Compliance with Pragmatic Marketing s That Work, LLC Project Whitepaper - Pragmatic Marketing's That Work Page 1 of 16 Introduction The Database has been designed for maximum flexibility

More information

UNDERGRADUATE COMPUTER SCIENCE EDUCATION: A NEW CURRICULUM PHILOSOPHY & OVERVIEW

UNDERGRADUATE COMPUTER SCIENCE EDUCATION: A NEW CURRICULUM PHILOSOPHY & OVERVIEW UNDERGRADUATE COMPUTER SCIENCE EDUCATION: A NEW CURRICULUM PHILOSOPHY & OVERVIEW John C. Knight, Jane C. Prey, & Wm. A. Wulf Department of Computer Science University of Virginia Charlottesville, VA 22903

More information