FACETs. Technical Report 05/19/2010
|
|
- Anissa Price
- 5 years ago
- Views:
Transcription
1 F3 FACETs Technical Report 05/19/2010
2 PROJECT OVERVIEW... 4 BASIC REQUIREMENTS... 4 CONSTRAINTS... 5 DEVELOPMENT PROCESS... 5 PLANNED/ACTUAL SCHEDULE... 6 SYSTEM DESIGN... 6 PRODUCT AND PROCESS METRICS... 8 METRIC DESCRIPTION... 8 METRIC RESULTS... 8 Results Per Release... 8 Defect Density... 9 Requirements Volatility... 9 PRODUCT STATE AT TIME OF DELIVERY... 9 REFLECTION P a g e
3 Revision History Name Date Reason For Changes Version Mike Phillips 05/19/10 Initial Creation P a g e
4 Project Overview The goal of this project was to create and enhance web-based tools that will assist engineers in designing quality products. The tools were part of a larger system that offers an open-source, real-time collaborative environment that allow engineers to seamlessly share and develop projects using a shared web interface. The first part was the existing Engineering Design Guide and Environment (EDGE) system. EDGE is a webbased project management system that handles user authentication, user permissions, and hosting of projects. Each project is then provided with its own project tools such as a SVN document repository and website. Most of the work of this project was on FACETs, a set of tools provided to each EDGE project. The FACETs tools are based off the FACETs concept which supports that all engineering processes can be broken up into twelve different phases of engineering or facets. Our work focused on three of the tools which addressed two of the early facets. We made enhancements to the objective tree tool which is part of the needs assessment facet and created the function tree and house of quality tools which belong to the concept development facet. An important feature of the system is the ability to track data integrity as data is shared and manipulated throughout the system. The house of quality tool is the first tool to handle this aspect and will likely serve as precedent for future tools. Basic Requirements Since the system already exists, the requirements for this project only deal with the portions of the system being developed by us. There are four areas from which these requirements are taken. These include adding several features to the objective tree tool, implementing the function tree tool, implementing the house of quality tool, and performing improvements to the system itself. The requirements for the objective tree mostly included improvements to the existing work. One requirement here was the ability for the moderator to delete desired nodes from the tree by clicking a button. The nodes also had to be rendered in such a way to display the name of the user who created it. The function tree tool did not exist before, so it had to be implemented. The function tree tool was similar to the objective tree. It had to be able to organize values entered by the user into a hierarchical tree. The function tree had to be drawn vertically, with the root node at the top. The moderator had to be able to delete nodes in this tool as in the objective tree. The House of Quality tool was the third area for our requirements. Only the correlation matrix room of the house had to be implemented. This tool had to present the user with a grid, where he could enter the correlation values that would go in a house of quality diagram. The column headers were taken from level 2 and 3 of a function tree session (where level 1 is the root). The user was allowed to select this session from a list of existing sessions. The row headers were done the same way as the column headers - with a selectable session, and using the 2nd and 3rd levels - but from an objective tree session instead of a function tree. 4 P a g e
5 Constraints The major constraining force behind this project was the fact that the system already existed. All work done by our team had to fit into the existing architecture. The programming languages were constrained somewhat by the fact that this was a web project, and certain languages are the standard way of doing things. For example, there wouldn't have been a choice about using JavaScript. The frameworks that were being used (such as jquery) were already integrated into the system too deeply to change. The database tables were also affected by these pre-determined constraints. With the way the PHP code for the database layer was written, every table was forced to have the two columns lastedit and lasteditor. The previous team's design of the data model for storing the objective tree nodes affected how we implemented the function tree and the house of quality. We opted to use the exact same table for the nodes in the function tree. When implementing the house of quality, this database structure made it difficult to put the headings into the correlation matrix. A special algorithm had to be written to parse this data into the proper form. Another constraint was simply that there were only four people on the team. There was a big learning curve to be able to work on the system. Each team member had to learn the project domain in order to understand how the tools will be used, and certain concepts such as house of quality. We also had to learn how the system worked in order to be able to develop new features for it. Development Process A custom process developed from aspects from Agile, Rapid Application Development (RAD), and Joint Application Design (JAD) methodologies rounded our hybrid methodology. We pulled points from these three models to fit the team's and project's needs and development style. Attributes of our process include: test-driven (acceptance) development incremental and flexible releases, dynamic requirements, and the possibility of prototyping. Following the agile development model, the team's focal point is incremental releases allowing for constant adaptation and inspection of requirements. RAD promotes quick, flexible, and content-filled releases without unnecessary time-consuming documentation. Most of the documentation derived from the acceptance testing including use cases and test cases. 5 P a g e
6 Figure 1 - RAD process compared to traditional development Both the project sponsor and advisor approved the process knowing that the iteration schedules and requirements were flexible. Since the sponsor attended at least one of the meetings each week, it proved very easy to communicate the status of our projects. The process' short release cycle also enforced communication to the sponsor and faculty advisor to report the status. There were no defined roles for the process except a metric gatherer for after each release. The cycle of our software was very short so the metrics gathered could not conclude anything. Planned/Actual Schedule Our planned project schedule consisted of 4 or 5 releases spanning 2 to 3 weeks in time. The first release was slated to begin January 31st, 2010, followed by our second release beginning March 8th, Because of the flexible nature of our schedule, the end date of the last release was unknown; however our absolute-end deadline was scheduled for May 22nd, Our actual schedule ended up as 4 releases each being between 2 and 4 weeks long. Our last release ended May 9th, Release 1 began and ended on time, although release 2 began a week late on March 15, Slippage in the schedule was mainly a result of the team underestimating implementation times. The only release that was greatly affected by this problem was release 3, which had to be extended one week past the limit of three weeks due to the implementation of the House of Quality. Also, the fifth release was deemed unfeasible due to end-of-quarter presentations and artifacts. System Design 6 P a g e
7 Since we were building on an existing system, many of the architectural decisions had already been made, but we still evaluated the architecture to ensure that it will meet future needs. There were several key aspects to the architecture. First, the database subsystem uses the PHP Pear package MDB2 which allows the underlying database to be abstracted away. So even though the production environment is using MySQL, other databases can easily be swapped in. There is also a custom set of classes used to perform the basic SQL commands like select, insert, update, and delete. We felt that the use of the MDB2 package improve the portability and modifiability of the system but the custom SQL command classes had several constraints and limitations that may affect the system in the future. The biggest limitation is the lack of a way to perform more complicated SQL commands such as joins. Though it had little effect on us, future teams may have to reevaluate the use of these classes or implement additional capabilities. Next, the EDGE PHP files are constructed in a very modular manner, making the system highly modifiable. This will be a great advantage as the system grows and additional features are implemented. This modularity helped us to reuse code when creating the function tree tool and made it easy for us to add the house of quality tool. Another design decision was the use of Smarty templating. Even though it is used in a minimalist way, it helps to separate the visual rendering from the underlying logic, which increases the system s modularity and improves maintainability. An additional aspect of the system is the flow of data throughout the tools. This will be a key aspect of the finished system, but is currently only being handled by the house of quality tool. To implement data integrity, a timestamp is attached to the data which helps to determine if the data has been modified by any tools. It is likely that in the future a more sophisticated approach will be required as the number and interdependencies of the tools increase. The last important aspect of the system is the synchronization of the tools. When the tools are being used, AJAX calls are used to synchronize changes between the clients and server. Currently, there is an AJAX poll every five seconds. The length of five seconds was to allow sufficient time for the server to process multiple requests as the number of users could grow quickly. The downside to the five seconds is the delay that users will experience even if there are only a few users. We discussed the possibility of 7 P a g e
8 implementing a variable length poll that would increase as the number of users on the system increase, but due to time and resource limits we chose to accept the current static five seconds. Product and Process Metrics Metric Description Two metrics were chosen: one for process and another for product. We focused on the process metric, requirement volatility, due to the nature of the product and the foreseen modifications of the system because of technology limitations. The other, product metric, emphasized defects contained in the product through the analysis of defect density. The first, requirement volatility, measured the number of functional requirements changes in given iterations of development. This measurement evaluated our progress in assessing the requirements defined for each iteration. Along with progress, it measured our ability to define and successfully elicit system requirements after each iteration for future releases. Throughout the development process, new requirements added to the list of previous requirements were not considered changes. After being accepted, changes to these new requirements were counted towards the process metric for that iteration. For the product metric, defect density was chosen as the most appropriate metric for our project. Defect density measured the number of reported defects versus lines of code written (excluding comments and whitespace). The metric measured the overall productivity of our team, but more importantly the quality of the product, itself. Since we were working from an existing system, there was an array of defects from the previous and current team's development. Metric Results Results Per Release Release 1: Defect Density: 1.36% Requirement Volatility: 40% Release 2: Defect Density: 1.06% Total Defect Density: 0.61% Requirement Volatility: 0% Total Requirement Volatility: 11% Release 3: Defect Density: 0.51% Total Defect Density: 0.93% Volatility: 0% Total Volatility: 7.7% 8 P a g e
9 Release 4: Defect Density: 0.83% Total Defect Density: 0.87% Volatility: 0 Total Volatility: 5.4% Defect Density The defect density was relatively low throughout the project. Each developer performed sufficient tests on his code before the end of the release, that most potential defects were prevented before the testing phase had begun. The defects that were found during testing and not resolved before the end of the release were usually eradicated early enough that they weren't included in the running total. Requirements Volatility The metric for requirement volatility was not used in a direct fashion. The team never looked at the volatility and took a specific action because of it. This is partly because we only had four releases, so there were not very many opportunities to react and change. Also, a lot of our requirements gathering was done up-front, so the majority of the requirements changes were caught early on. This led to a high volatility at the beginning and low volatility thereafter. The team did use this data indirectly. During every requirements gathering session with the sponsor, each team member kept in mind that volatility was being measured. As a result, the team tried very hard to capture the requirements right the first time. Product State at Time of Delivery We have finished the implementation of the Function Tree and the basic House Of Quality tool as planned. Most of the features that we planned have been added, although we were not able to implement a new visual system for drawing the Objective and Function Trees as we had hoped. We had originally planned on fixing some existing issues with the Affinity Diagram tool. We later decided that this was out of the scope of our work as we wanted to concentrate on the tools that we were creating. Server load testing had also been discussed at the beginning of the project. While our test server was unofficially tested during user testing, no formal stress testing was performed. In fulfilling our requirements we were able to fix multiple defects that existed from the previous teams' work. Some of those defects, for example, involved problems with creating and editing sessions. Overall, we feel we have finished roughly 85% of the original requirements we listed, as well as multiple extra endeavors. 9 P a g e
10 Reflection This was a very successful project overall so a good amount went right, but there are always obstacles and attributes that would like to have been changed. Communication was an aspect of the project that went well. We were able to keep in constant contact with our sponsor and each other. The process methodology was easy to follow and allowed for revision without causing any observable setback on the project. The metrics we set to track were facilitated by the process. Schedule slippage and documentation that added no value were two facets of the project that we would have re-evaluated if done over. Our schedule slipped twice, but we still ended up completing 85% of the requirements set in the beginning of the project. Some of the documentation we chose to complete, we did not start because it (collaboration diagram) would have added no value to our project. Also, some of the documentation, though completed for each release (use cases), was ultimately ignored. If re-doing this project or continuing, we would make a better schedule and adhere to it more strictly. We would choose better documentation that we utilized constantly throughout the project for future teams. Since this was an already existing project, we had to continue the work and change code according to our design of new tools. We would have chosen a slightly different technology base that would have been more suitable for this project. Overall, we learned team cooperation on a longer term project compared to the usual project within our 10-week courses. We learned how to take the requirements from our sponsor and transform them into a working product. Communication with the sponsor was probably not like in industry because our sponsor was almost always accessible and constantly providing feedback. 10 P a g e
Co-op Housing Portal
Co-op Housing Portal Team HAL Peter Ess, Megan Kukielka, Matthew Mazaika, Christopher Moyer, Jeremy Petko RIT Office of Cooperative Education and Career Services Jim Bondi Nathan Sarr Faculty Mentor Project
More informationContent Management & Generation System
Content Management & Generation System Project Overview ACM SIGSOFT publishes a bi-monthly hybrid Newsletter called Software Engineering Notes (SEN). The Newsletter is manually assembled by the editor,
More informationSample Exam. Advanced Test Automation - Engineer
Sample Exam Advanced Test Automation - Engineer Questions ASTQB Created - 2018 American Software Testing Qualifications Board Copyright Notice This document may be copied in its entirety, or extracts made,
More informationIntegration With the Business Modeler
Decision Framework, J. Duggan Research Note 11 September 2003 Evaluating OOA&D Functionality Criteria Looking at nine criteria will help you evaluate the functionality of object-oriented analysis and design
More informationAdopting Agile Practices
Adopting Agile Practices Ian Charlton Managing Consultant ReleasePoint Software Testing Solutions ANZTB SIGIST (Perth) 30 November 2010 Tonight s Agenda What is Agile? Why is Agile Important to Testers?
More informationA Simple Course Management Website
A Simple Course Management Website A Senior Project Presented to The Faculty of the Computer Engineering Department California Polytechnic State University, San Luis Obispo In Partial Fulfillment Of the
More information10 Steps to Building an Architecture for Space Surveillance Projects. Eric A. Barnhart, M.S.
10 Steps to Building an Architecture for Space Surveillance Projects Eric A. Barnhart, M.S. Eric.Barnhart@harris.com Howard D. Gans, Ph.D. Howard.Gans@harris.com Harris Corporation, Space and Intelligence
More informationSystem Development Life Cycle Methods/Approaches/Models
Week 11 System Development Life Cycle Methods/Approaches/Models Approaches to System Development System Development Life Cycle Methods/Approaches/Models Waterfall Model Prototype Model Spiral Model Extreme
More informationSoftware Life Cycle. Main issues: Discussion of different life cycle models Maintenance or evolution
Software Life Cycle Main issues: Discussion of different life cycle models Maintenance or evolution Introduction software development projects are large and complex a phased approach to control it is necessary
More informationSoftware Development Methodologies
Software Development Methodologies Lecturer: Raman Ramsin Lecture 8 Agile Methodologies: XP 1 extreme Programming (XP) Developed by Beck in 1996. The first authentic XP book appeared in 1999, with a revised
More informationMajor Topics. Prototyping and Rapid Application Development
Prototyping Major Topics Prototyping concepts Types of prototypes Prototyping and the systems development life cycle Prototype development guidelines Prototype evaluation Rapid application development
More informationEuro-BioImaging Preparatory Phase II Project
Euro-BioImaging Preparatory Phase II Project Testing of the basic framework of EuBI online user access portal, with the most central links and functions included, and improvements and corrections implemented
More informationHighly Accurate Mobile Device Positioning based on Wi-Fi signals
Highly Accurate Mobile Device Positioning based on Wi-Fi signals Team Braintrust Brandon Pastuszek Sam Gottfried Joe Impellizzieri Ankur Patel Jeff Seaman Project Sponsor ZOS Commuications Faculty Coach
More informationTest Plan. Co-op Evaluation System. Senior Project Team Members: Tyler Geery Maddison Hickson Casey Klimkowsky Emma Nelson.
Test Plan Co-op Evaluation System Senior Project 2014-2015 Team Members: Tyler Geery Maddison Hickson Casey Klimkowsky Emma Nelson Faculty Coach: Samuel Malachowsky Project Sponsors: Jim Bondi (OCSCE)
More informationDatabase Systems: Design, Implementation, and Management Tenth Edition. Chapter 9 Database Design
Database Systems: Design, Implementation, and Management Tenth Edition Chapter 9 Database Design Objectives In this chapter, you will learn: That successful database design must reflect the information
More informationAssignments. Assignment 2 is due TODAY, 11:59pm! Submit one per pair on Blackboard.
HCI and Design Assignments Assignment 2 is due TODAY, 11:59pm! Submit one per pair on Blackboard. Today Paper prototyping An essential tool in your design toolbox! How do we design things that actually
More informationSOFTWARE LIFE-CYCLE MODELS 2.1
SOFTWARE LIFE-CYCLE MODELS 2.1 Outline Software development in theory and practice Software life-cycle models Comparison of life-cycle models 2.2 Software Development in Theory Ideally, software is developed
More informationQuality Management Plan (QMP)
Quality Management Plan (QMP) LEMA Pilot School Integrated Scheduling System. Team number 12 Name Primary Role Secondary Role David Wiggins Project Manager Developer Aakash Shah Prototyper Developer Kushalpreet
More informationProject Plan. SISCalendar. for. Prepared by Zach Masiello. Ethan Mick Michael Caputo Shawn Thompson Organization: SIS.io
Project Plan for SISCalendar Prepared by Zach Masiello Ethan Mick Michael Caputo Shawn Thompson Organization: SIS.io Revision History Name Date Reason For Changes Version Initial 10/1/13 First version
More information01/09: Project Plan. The Capstone Experience. Dr. Wayne Dyksen Department of Computer Science and Engineering Michigan State University Spring 2013
01/09: Project Plan The Capstone Experience Dr. Wayne Dyksen Department of Computer Science and Engineering Michigan State University Spring 2013 From Students to Professionals Project Plan Functional
More informationAudit. A Senior Project presented to the Faculty of the Computer Science Department California Polytechnic State University, San Luis Obispo
Audit A Senior Project presented to the Faculty of the Computer Science Department California Polytechnic State University, San Luis Obispo In Partial Fulfillment of the Requirements for the Degree Bachelor
More informationImproved Database Development using SQL Compare
Improved Database Development using SQL Compare By David Atkinson and Brian Harris, Red Gate Software. October 2007 Introduction This white paper surveys several different methodologies of database development,
More informationBusiness Analysis for Practitioners - Requirements Elicitation and Analysis (Domain 3)
Business Analysis for Practitioners - Requirements Elicitation and Analysis (Domain 3) COURSE STRUCTURE Introduction to Business Analysis Module 1 Needs Assessment Module 2 Business Analysis Planning Module
More informationCASE STUDY IT. Albumprinter Adopting Redgate DLM
CASE STUDY IT Albumprinter Adopting Redgate DLM "Once the team saw they could deploy all their database changes error-free at the click of a button, with no more manual scripts, it spread by word of mouth.
More informationPerfect Timing. Alejandra Pardo : Manager Andrew Emrazian : Testing Brant Nielsen : Design Eric Budd : Documentation
Perfect Timing Alejandra Pardo : Manager Andrew Emrazian : Testing Brant Nielsen : Design Eric Budd : Documentation Problem & Solution College students do their best to plan out their daily tasks, but
More informationFormal Verification of ASIC Design
Worcester Polytechnic Institute Digital WPI Major Qualifying Projects (All Years) Major Qualifying Projects April 2018 Formal Verification of ASIC Design Jonathan Ariza Worcester Polytechnic Institute
More informationCOMP6471 WINTER User-Centered Design
COMP6471 WINTER 2003 User-Centered Design Instructor: Shahriar Ameri, Ph.D. Student: Pedro Maroun Eid, ID# 5041872. Date of Submission: Monday, March 10, 2003. (Week 9) Outline Outline... 2 ABSTRACT...3
More information1. Introduction and overview
1. Introduction and overview 1.1 Purpose of this Document This document describes how we will test our code for robustness. It includes test cases and other methods of testing. 1.2 Scope of the Development
More informationCollegiate Times Grades
Collegiate Times Grades By: James O Hara, Hang Lin CS4624 Multimedia, Hypertext, and Information Access Virginia Tech Blacksburg, Va. May 4, 2014 Client: Alex Koma, Managing Editor, Collegiate Times Table
More informationUser Documentation Development Life Cycle (UDDLC)
WWW.ALMAHACONSULTING.CA User Documentation Development Life Cycle (UDDLC) STANDARD OPERATING PROCEDURE BUSINESS PROCESS DOCUMENT DOCUMENT STATUS: VERSION 0.1 Department BUSINESS TRANSFORMATION Process
More informationMedia Services Online Mohammed Abukhiran. Report 13 on the work of Week 13
Media Services Online Mohammed Abukhiran Report 13 on the work of Week 13 Berea College Nov 30, 2010 Application Development Project Concept Proposal Media Services at Berea College uses Voyger (Database
More informationAssignment 8 rekindl Local Community (1:30PM) Meet The Team. Ryan C. Amanda L. Sara V. James C.
Hi-Fi Prototype Assignment 8 rekindl Local Community (1:30PM) Meet The Team Ryan C. Amanda L. Sara V. James C. Introduction Mission Statement: Reignite faded friendships. Problem Overview: Busy schedules
More informationAn Honors Thesis (HONRS 499) Thesis Advisor Rui Chen. Ball State University Muncie, Indiana. Expected Date of Graduation
The Development of BeatCred.net An Honors Thesis (HONRS 499) by Peter Kaskie Thesis Advisor Rui Chen Ball State University Muncie, Indiana May 2012 Expected Date of Graduation May 2012 Peter Kaskie The
More informationChapter 4 Objectives
Chapter 4 Objectives Eliciting requirements from the customers Modeling requirements Reviewing requirements to ensure their quality Documenting requirements for use by the design and test teams 4.1 The
More informationCPU DB Data Visualization Senior Project Report
CPU DB Data Visualization Senior Project Report Marek Moreno ( mmoren14@calpoly.edu ) Ruchita Patel ( rpatel31@calpoly.edu ) 16 June 2017 Introduction Project Overview/Executive Summary Given the CPU database
More informationPolyratings Website Update
Polyratings Website Update Senior Project Spring 2016 Cody Sears Connor Krier Anil Thattayathu Outline Overview 2 Project Beginnings 2 Key Maintenance Issues 2 Project Decision 2 Research 4 Customer Survey
More informationTopic 01. Software Engineering, Web Engineering, agile methodologies.
Topic 01 Software Engineering, Web Engineering, agile methodologies. 1 What is Software Engineering? 2 1 Classic Software Engineering The IEEE definition: Software Engineering is the application of a disciplined,
More informationGraphic Design Conversation
Aneto Okonkwo 12/12/06 CS377B Graphic Design Conversation Introduction This document describes the design process and results of a project focused on modeling collaborative graphic design on a whiteboard
More informationComputer Vision Based Route Mapping
Computer Vision Based Route Mapping by Ryan Kehlenbeck and Zack Cody Department of Computer Science and Software Engineering California Polytechnic State University, San Luis Obispo June 2017 Abstract
More informationSix Sigma in the datacenter drives a zero-defects culture
Six Sigma in the datacenter drives a zero-defects culture Situation Like many IT organizations, Microsoft IT wants to keep its global infrastructure available at all times. Scope, scale, and an environment
More informationAn Introduction to JavaScript & Bootstrap Basic concept used in responsive website development Form Validation Creating templates
PHP Course Contents An Introduction to HTML & CSS Basic Html concept used in website development Creating templates An Introduction to JavaScript & Bootstrap Basic concept used in responsive website development
More informationJIRA Studio Use Cases and Tutorial basis
JIRA Studio Use Cases and Tutorial basis Analysis of usefulness of JIRA Studio Eclipse tool-chain Tolga Tuncbilek, Elisa Kallio, Shiyuan Wang, Viktor Porvaznik Table of Contents 1 Introduction... 3 2 Data
More informationPromoting Component Architectures in a Dysfunctional Organization
Promoting Component Architectures in a Dysfunctional Organization by Raj Kesarapalli Product Manager Rational Software When I first began my career as a software developer, I didn't quite understand what
More informationAutomated Testing of Tableau Dashboards
Kinesis Technical Whitepapers April 2018 Kinesis CI Automated Testing of Tableau Dashboards Abstract Companies make business critical decisions every day, based on data from their business intelligence
More informationSystems Analysis & Design
Systems Analysis & Design Dr. Ahmed Lawgali Ahmed.lawgali@uob.edu.ly Slide 1 Systems Analysis & Design Course Textbook: Systems Analysis and Design With UML 2.0 An Object-Oriented Approach, Second Edition
More informationTRANSITIONING PROJECTS TO A MODEL-BASED APPROACH
: Distribution Statement A. Approved for public release; release is unlimited. 2017 NDIA GROUND VEHICLE SYSTEMS ENGINEERING AND TECHNOLOGY SYMPOSIUM SYSTEMS ENGINEERING (SE) TECHNICAL SESSION AUGUST 8-10,
More informationHTML5 Report Creator Colorado School of MInes Field Session 2014 June 17, 2014
HTML5 Report Creator Colorado School of MInes Field Session 2014 June 17, 2014 Tyler Lyons Anthony Nguyen Kolten Robison Table of Contents Client Background & Product Vision 3 Requirements 4 System Architecture
More informationPivotal Tracker Kanban Prototype COLORADO SCHOOL OF MINES 2017 FIELD SESSION
Pivotal Tracker Kanban Prototype COLORADO SCHOOL OF MINES 2017 FIELD SESSION Ann Gustafson Emily Dederick Christopher Bonin Gerald Ung CLIENT Morgan Whitney Table of Contents 1. Introduction... 2 1.1.
More informationPORTAL RESOURCES INFORMATION SYSTEM: THE DESIGN AND DEVELOPMENT OF AN ONLINE DATABASE FOR TRACKING WEB RESOURCES.
PORTAL RESOURCES INFORMATION SYSTEM: THE DESIGN AND DEVELOPMENT OF AN ONLINE DATABASE FOR TRACKING WEB RESOURCES by Richard Spinks A Master s paper submitted to the faculty of the School of Information
More informationThe main website for Henrico County, henrico.us, received a complete visual and structural
Page 1 1. Program Overview The main website for Henrico County, henrico.us, received a complete visual and structural overhaul, which was completed in May of 2016. The goal of the project was to update
More informationCS595 APPLICATION DEVELOPMENT FOR MOBILE DEVICES
CS595 APPLICATION DEVELOPMENT FOR MOBILE DEVICES PROJECT ASSIGNMENT FINAL REPORT PRESENTED BY THE DROID GEEKS ASHOK KUMAR JONNALAGADDA R. J. LEWIS III DESCRIPTION Team Droid Geeks has assisted the Old
More informationJoyner Library EAD-Delivery Redesign
Joyner Library EAD-Delivery Redesign which has resulted in twenty-nine additional events connecting Capus Waynick to Anastasia Somoza By Mark Custer August 11, 2010 Guiding Principles 1. Avoid altering
More information09/07: Project Plan. The Capstone Experience. Dr. Wayne Dyksen Department of Computer Science and Engineering Michigan State University Fall 2016
09/07: Project Plan The Capstone Experience Dr. Wayne Dyksen Department of Computer Science and Engineering Michigan State University Fall 2016 From Students to Professionals Project Plan Functional Specifications
More informationCOMP 354 Introduction to Software Engineering
COMP 354 Introduction to Software Engineering Greg Butler Office: EV 3.219 Computer Science and Software Engineering Concordia University, Montreal, Canada Email: gregb@cs.concordia.ca Winter 2015 Course
More informationChapter 1: Introduction to Systems Analysis
Systems Analysis and Design With UML 2.0 An Object-Oriented Oriented Approach, Second Edition Chapter 1: Introduction to Systems Analysis and Design Alan Dennis, Barbara Wixom, and David Tegarden 2005
More informationUnit Notes. ICAWEB501A Build a dynamic website Topic 4 Test web application
Unit Notes ICAWEB501A Build a dynamic website Topic 4 Test web application Copyright, 2014 by TAFE NSW - North Coast Institute Date last saved: 10 March 2014 by Amanda Walker Version: 1.0 # of Pages =
More informationAutomated Web Application Testing Using Selenium
Worcester Polytechnic Institute Digital WPI Major Qualifying Projects (All Years) Major Qualifying Projects March 2017 Automated Web Application Testing Using Selenium Benjamin I. Chaney Worcester Polytechnic
More informationObject Oriented Programming
Binnur Kurt kurt@ce.itu.edu.tr Istanbul Technical University Computer Engineering Department 1 Version 0.1.2 About the Lecturer BSc İTÜ, Computer Engineering Department, 1995 MSc İTÜ, Computer Engineering
More informationExperience with Change-oriented SCM Tools
Experience with Change-oriented SCM Tools Ivica Crnkovic ABB Industrial Systems AB, 721 67 Västerås, Sweden E-mail: ivica@sw.seisy.abb.se Abstract. In the recent years two approaches in Software Configuration
More informationINTRODUCTION. 2. User-centred interface design.
INTRODUCTION 2. User-centred interface design User-Centred Design ISO 9241-210 : Human-centred design for interactive systems Meets requirements Plan the user centred process 4. Evaluation against requirements
More informationHistory of object-oriented approaches
Prof. Dr. Nizamettin AYDIN naydin@yildiz.edu.tr http://www.yildiz.edu.tr/~naydin Object-Oriented Oriented Systems Analysis and Design with the UML Objectives: Understand the basic characteristics of object-oriented
More informationGENERATION TOOL FOR DBMS FOCUSED APPLICATIONS
GENERATION TOOL FOR DBMS FOCUSED APPLICATIONS Carlos del Cuvillo Universidad Politecnica de Madrid Ctra. de Valencia km. 7 E28031 Madrid Hector Garcia Universidad Politecnica de Madrid Ctra. de Valencia
More informationSymbiant Tracker Auditee Guide. Version 4.4. Auditee Guide
Version 4.4 Auditee Guide 1 revision 3.4 This auditee guide is for Symbiant Tracker 4.4 only (Standard and Pro) Copyright 2005 2011 Symbiant. All rights reserved. Symbiant is a Trade Mark of Credit Card
More informationGENGHIS, AN AUTHORING TOOL FOR KHAN ACADEMY EXERCISES
UNIVERSIDAD CARLOS III DE MADRID ESCUELA POLITÉCNICA SUPERIOR BACHELOR IN TELEMATICS ENGINEERING EXTENDED SUMMARY GENGHIS, AN AUTHORING TOOL FOR KHAN ACADEMY EXERCISES Author: Juan Luis Sanz Moreno Supervisor:
More informationObjectives. Connecting with Computer Science 2
Objectives Learn how software engineering is used to create applications Learn some of the different software engineering process models Understand what a design document is and how it should be used during
More informationFeasibility Evidence Description (FED)
Feasibility Evidence Description (FED) United Direct Marketing Team 9 Fall Semester Chun-Ling Chen Project manager/ Prototyper Chun-Pei Su Lifecycle Planner Shao-yen Cheng System Architect Yuan-Chang Chang
More information1. I NEED TO HAVE MULTIPLE VERSIONS OF VISUAL STUDIO INSTALLED IF I M MAINTAINING APPLICATIONS THAT RUN ON MORE THAN ONE VERSION OF THE.
CUSTOMER PAIN POINTS 1. I NEED TO HAVE MULTIPLE VERSIONS OF VISUAL STUDIO INSTALLED IF I M MAINTAINING APPLICATIONS THAT RUN ON MORE THAN ONE VERSION OF THE.NET FRAMEORK. THAT S TAKING UP SPACE ON MY HARDDRIVE
More informationPHP & PHP++ Curriculum
PHP & PHP++ Curriculum CORE PHP How PHP Works The php.ini File Basic PHP Syntax PHP Tags PHP Statements and Whitespace Comments PHP Functions Variables Variable Types Variable Names (Identifiers) Type
More informationInteractive (High-fi) Prototype (Group)
Interactive (High-fi) Prototype (Group) Midway Milestone due at the start of your studio (Thursday/Friday Dec 1-2) Final Prototype due at the start of your studio (Thursday/Friday Dec 8-9) Writeup due
More informationRelease Notes March 2016
Release Notes March 2016 About the Release Notes... 3 Release Overview... 3 End of Life Announcements... 3 Other Announcements... 5 Enhancements... 6 Doc Launcher for uploading 3 rd party documents and
More informationBuilding a New Rational Web Site with Rational Suite
Building a New Rational Web Site with Rational Suite by Christina Howe Director of Internet Services Rational Software In April of last year, Rational Software determined that its Web site no longer measured
More informationBooks by Michael R. Ault
Michael R. Ault Oracle Guru The Myth of Database Independence Mike Ault Oracle Guru Texas Memory Systems - Nuclear Navy 6 years - Nuclear Chemist/Programmer 10 years - Kennedy Western University Graduate
More informationA Working Paper of the EastWest Institute Breakthrough Group. Increasing the Global Availability and Use of Secure ICT Products and Services
A Working Paper of the EastWest Institute Breakthrough Group Increasing the Global Availability and Use of Secure ICT Products and Services August 5, 2015 The EastWest Institute (EWI) is leading a Global
More informationDevelopment of Educational Software
Development of Educational Software Rosa M. Reis Abstract The use of computer networks and information technology are becoming an important part of the everyday work in almost all professions, especially
More informationPassionate designer with a love for solving design problems using feasible and creative solutions
Ramya Jayakumar Mobile: 980-430-9942 Email: ramyajayakumar7@gmail.com Portfolio:www.ramyajayakumar.com Summary Passionate designer with a love for solving design problems using feasible and creative solutions
More informationSoftware Architecture
Software Architecture Does software architecture global design?, architect designer? Overview What is it, why bother? Architecture Design Viewpoints and view models Architectural styles Architecture asssessment
More informationUNIT-I Introduction of Object Oriented Modeling
UNIT-I Introduction of Object Oriented Modeling - Prasad Mahale Object Oriented Modeling and Reference Books: Design 1. Grady Booch, James Rumbaugh, Ivar Jacobson Unified Modeling Language User Guide,
More informationLiberate, a component-based service orientated reporting architecture
Paper TS05 PHUSE 2006 Liberate, a component-based service orientated reporting architecture Paragon Global Services Ltd, Huntingdon, U.K. - 1 - Contents CONTENTS...2 1. ABSTRACT...3 2. INTRODUCTION...3
More informationProgramming Languages and Program Development
Programming Languages and Program Development 1 Programming Languages and How They Work Programming o Process used to create software programs Programmers o People who use programming languages to create
More information3Lesson 3: Web Project Management Fundamentals Objectives
3Lesson 3: Web Project Management Fundamentals Objectives By the end of this lesson, you will be able to: 1.1.11: Determine site project implementation factors (includes stakeholder input, time frame,
More informationChapter 5. Software Tools
Chapter 5 Software Tools 1 Introduction The demands of modern life require user-interface architects to build reliable, standard, safe, inexpensive, effective, and widely acceptable user interfaces on
More informationLab 1 MonarchPress Product Description. Robert O Donnell. Old Dominion University CS411. Janet Brunelle. November 23, 2015.
Running Head: LAB 1 MONACHPRESS PRODUCT DESCRIPTION Lab 1 MonarchPress Product Description Robert O Donnell Old Dominion University CS411 Janet Brunelle November 23, 2015 Version #3 1 2 Table of Contents
More information09/06: Project Plan. The Capstone Experience. Dr. Wayne Dyksen Department of Computer Science and Engineering Michigan State University Fall 2017
09/06: Project Plan The Capstone Experience Dr. Wayne Dyksen Department of Computer Science and Engineering Michigan State University Fall 2017 From Students to Professionals Project Plan Functional Specifications
More information(Objective-CS605 Software Engeenring-II)
Which one of the following is NOT a useful indicator of software quality? Correctness Code size (Page 67) Maintainability Integrity Usability Which one of the following does not belong to a strategy for
More informationDesign concepts for data-intensive applications
6 th International Conference on Applied Informatics Eger, Hungary, January 27 31, 2004. Design concepts for data-intensive applications Attila Adamkó Department of Information Technology, Institute of
More informationCase 1:98-cv CKK Document Filed 06/15/2006 Page 1 of 7 IN THE UNITED STATES DISTRICT COURT FOR THE DISTRICT OF COLUMBIA
Case 1:98-cv-01232-CKK Document 831-1 Filed 06/15/2006 Page 1 of 7 IN THE UNITED STATES DISTRICT COURT FOR THE DISTRICT OF COLUMBIA UNITED STATES OF AMERICA, v. Plaintiff, MICROSOFT CORPORATION, Civil
More informationData Marting Crime Correlations Using San Francisco Crime Open Data
Data Marting Crime Correlations Using San Francisco Crime Open Data Kiel Gordon Matt Pymm John Tuazon California State University Sacramento CSC 177 Data Warehousing and Data Mining Dr. Lu May 16, 2016
More informationStrategies for Rapid Development in Internet Time. William A. Cunningham December 5, 2000 NYOUG New York, NY
Strategies for Rapid Development in Internet Time William A. Cunningham December 5, 2000 NYOUG New York, NY Background - Issues Productivity differences can be 10 to 1 in developing systems in the same
More informationGradational conception in Cleanroom Software Development
Gradational conception in Cleanroom Software Development Anshu Sharma 1 and Shilpa Sharma 2 1 DAV Institute of Engineering and Technology, Kabir Nagar, Jalandhar, India 2 Lovely Professional University,
More informationFull Stack Web Developer
Full Stack Web Developer S.NO Technologies 1 HTML5 &CSS3 2 JavaScript, Object Oriented JavaScript& jquery 3 PHP&MYSQL Objective: Understand the importance of the web as a medium of communication. Understand
More informationHPE ALM Standardization as a Precursor for Data Warehousing March 7, 2017
HPE ALM Standardization as a Precursor for Data Warehousing March 7, 2017 Brought to you by the Vivit Business Intelligence Special Interest Group led by Oded Tankus Hosted By Oded Tankus Project Manager
More informationIntroduction. Chapter 1. What Is Visual Modeling? The Triangle for Success. The Role of Notation. History of the UML. The Role of Process
Quatrani_Ch.01.fm Page 1 Friday, October 27, 2000 9:02 AM Chapter 1 Introduction What Is Visual Modeling? The Triangle for Success The Role of Notation History of the UML The Role of Process What Is Iterative
More informationFIVE BEST PRACTICES FOR ENSURING A SUCCESSFUL SQL SERVER MIGRATION
FIVE BEST PRACTICES FOR ENSURING A SUCCESSFUL SQL SERVER MIGRATION The process of planning and executing SQL Server migrations can be complex and risk-prone. This is a case where the right approach and
More informationCourse Title: Enterprise Web Development Instructor: Dr. Michael Bigrigg
Course Information* Course Title: 95882 Enterprise Web Development Instructor: Dr. Michael Bigrigg (bigrigg@andrew.cmu.edu) Prerequisites (if applicable) Previous Programming Course. This course assumes
More informationSoftware Engineering Lifecycles. Controlling Complexity
Software Engineering Lifecycles Class url:http://laser.cs.umass.edu/courses/cs320.spring11/ Controlling Complexity Separation of Concerns Planning Ahead Do a little work now to make later work easier The
More informationBPS Suite and the OCEG Capability Model. Mapping the OCEG Capability Model to the BPS Suite s product capability.
BPS Suite and the OCEG Capability Model Mapping the OCEG Capability Model to the BPS Suite s product capability. BPS Contents Introduction... 2 GRC activities... 2 BPS and the Capability Model for GRC...
More informationProject. Minpeng Zhu
Project Minpeng Zhu Groups of 4 (3-5) Form groups I want the following information from each group: Names, personal numbers, e-mail addresses Contact person ( project leader ) Deadline for group formation:
More informationFormStream a Workflow Prototyping Tool for Classroom Use
FormStream a Workflow Prototyping Tool for Classroom Use Paul Juell and Benjamin Dischinger Department of Computer Science North Dakota State University Computer Science NDSU Fargo, ND 58105 paul.juell@ndsu.edu
More informationWhat is the Joint Application Development (JAD) Process?
What is the Joint Application Development (JAD) Process? By Joy Matthews, Vice President, Pierson Requirements Group, Inc. jmatthews@piersonrequirementsgroup.com JAD is an Important Technique for Software
More informationSocial Networking. A video sharing community website. Executive Summary. About our Client. Business Situation
Social Networking A video sharing community website. Executive Summary The client firm had a couple of social networking video sharing community websites that were hosted using a freely available open
More information