CSC340S Asst3 Information System Design Detailed Marking Scheme



Similar documents
System Development and Life-Cycle Management (SDLCM) Methodology. Approval CISSCO Program Director


White Paper: Establishing a Configuration Management Database Schema: A Working Model

Chapter 10 Practical Database Design Methodology and Use of UML Diagrams

Swirl. Multiplayer Gaming Simplified. CS4512 Systems Analysis and Design. Assignment Marque Browne Manuel Honegger

Operating Systems. Module Descriptor

Release: 1. ICTSAD505 Develop technical requirements for business solutions

UML Diagram Types. Use Cases do the Following. Use Case Diagram

MIDLANDS STATE UNIVERSITY

FUNCTIONAL SKILLS ENGLISH - WRITING LEVEL 2

CSC340S - Information Systems Analysis and Design

Copyright bizagi

Information Systems Analysis and Design CSC John Mylopoulos. Software Architectures Information Systems Analysis and Design CSC340

Use Cases. Massimo Felici. Massimo Felici Use Cases c

Designing Real-Time and Embedded Systems with the COMET/UML method

Department of Information Technology ENTD311: Analysis and Design of Information Systems 3 Credit Hours 8 Weeks Prerequisite(s): None

Software Engineering/Courses Description Introduction to Software Engineering Credit Hours: 3 Prerequisite: (Computer Programming 2).

Team Quicken Loans: Mobile RFID Inventory Tracking System. Project Plan. Spring 2014

Software Architecture Document

PS: Presentation software

White Paper. ThinRDP Load Balancing

TABLE OF CONTENT CHAPTER TITLE PAGE TITLE DECLARATION DEDICATION ACKNOWLEDGEMENTS ABSTRACT ABSTRAK

Scheme G. Sample Test Paper-I

SAMPLE IT CONTINGENCY PLAN FORMAT

Use Cases. Use Cases Diagrams

Object-Oriented Systems Analysis and Design

Software Architecture for Paychex Out of Office Application

SYSTEMS AND SOFTWARE REQUIREMENTS SPECIFICATION (SSRS) TEMPLATE. Version A.4, January 2014 FOREWORD DOCUMENT CONVENTIONS

Applying 4+1 View Architecture with UML 2. White Paper

Implementing a Data Warehouse with Microsoft SQL Server

Microsoft SQL Database Administrator Certification

STATE OF NEVADA Department of Administration Division of Human Resource Management CLASS SPECIFICATION

Automating Rich Internet Application Development for Enterprise Web 2.0 and SOA

VALLIAMMAI ENGNIEERING COLLEGE SRM Nagar, Kattankulathur DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING

COSC 3351 Software Design. Recap for the first quiz. Edgar Gabriel. Spring For the 1 st Quiz

No Evidence. 8.9 f X

Chapter 10. Practical Database Design Methodology. The Role of Information Systems in Organizations. Practical Database Design Methodology

Software Architecture Action Guide. Why do we care about Software Architecture?

Course Name: Course in JSP Course Code: P5

Roadmap. Software Engineering. Software Engineering. Project Life Cycle. Database. Project Lifecycle

Contents. Introduction and System Engineering 1. Introduction 2. Software Process and Methodology 16. System Engineering 53

How To Be A Database Administrator

Patterns in Software Engineering

Clarifying a vision on certification of MDA tools

ÇANKAYA UNIVERSITY. BASIC AND ELECTIVE COURSES ENGLISH UNIT Course Definition Form. Number of. hours. Course Type Check all that are applicable

Course 10777A: Implementing a Data Warehouse with Microsoft SQL Server 2012

Software Engineering UNIT -1 OVERVIEW

Surround SCM Backup and Disaster Recovery Solutions

game development documentation game development documentation: concept document

Software Development in the Large!

Implementing a Data Warehouse with Microsoft SQL Server 2012

ICTICT403 Apply software development methodologies

Project QA and Collaboration Plan for <project name>

Architecture. Reda Bendraou

SOFTWARE DEVELOPMENT PLAN

Creating the Conceptual Design by Gathering and Analyzing Business and Technical Requirements

2.2 INFORMATION SERVICES Documentation of computer services, computer system management, and computer network management.

Implementing a Data Warehouse with Microsoft SQL Server 2012

CHAPTER 1 INTRODUCTION

Software Architecture Document

Department of Engineering Technology Assessment Progress Report Calendar Year 2011 (prepared March 2012)

1. Dimensional Data Design - Data Mart Life Cycle

Chap 1. Introduction to Software Architecture

ITS Projects Systems Engineering Process Compliance Checklist

Designing a Database Schema

Computerisation and Performance Evaluation

Principles of Database. Management: Summary

TRUCKEE DONNER RECREATION & PARK DISTRICT INFORMATION TECHNOLOGY ADMINISTRATOR

The University of Adelaide Business School

Implementing a Data Warehouse with Microsoft SQL Server 2014

THE BCS PROFESSIONAL EXAMINATIONS Diploma. April 2006 EXAMINERS REPORT. Systems Design

CMPT 354 Database Systems. Simon Fraser University Summer Instructor: Oliver Schulte

Requirements Document for the Banking System. Lecture # 40

ICTWEB512 Administer business websites and servers

Rotorcraft Health Management System (RHMS)

Microsoft Infrastructure Assessment

Introduction to Network Security. Topics

Homework #2 solutions

Red Hat Enterprise Portal Server: Architecture and Features

Client-server 3-tier N-tier

Writing Reports BJECTIVES ONTENTS. By the end of this section you should be able to :

RFP Attachment C Classifications

This presentation provides an overview of the architecture of the IBM Workload Deployer product.

7. Business views (2/3h)

Design Document Version 0.0

Transcription:

CSC340S Asst3 Information System Design Detailed Marking Scheme Marker: Team: Total Marks: /101 Marks for this assignment depend on the factors listed below. A: Global Architecture (20%). Description and justification of the hardware, networking and software platform selected for the design; also, description and justification of the software architecture adopted. Value 20 _ Specification of the computer network (existing or new) Specification of the hardware (existing or new) Specification of the software platform (operating system and other commercial software you will be using for your system) Specification of the software architecture, for example, clientserver, MVC, layered, etc Identification of sub-systems and major components Justification that the overall design meets all requirements

B: Program Design (21%). A description of the detailed design of the application component of the system, given in terms of class, sequence, and state diagrams. Value: 21 B1. Class Diagrams (7%) Value: 7 (Informal) Description of class diagrams. ( ) Little understanding of class diagrams. ( ) Reasonable diagrams, but not enough to capture the design of the application and/or there is missing information from some diagrams, e.g., attributes, operations, multiplicities B2. Sequence Diagrams (7%) Value: 7 (Informal) Description of sequence diagrams. ( ) Little understanding of sequence diagrams.

( ) Reasonable diagrams, but not enough to capture the design of the application and/or there is missing information from some diagrams, e.g., conditional branching or terminations B3. Statechart Diagrams (7%) Value: 7 (Informal) Description of statechart diagrams. ( ) Little understanding of statechart diagrams. ( ) Reasonable diagrams, but not enough to capture the design of the application and/or there is missing information from some diagrams, e.g., events, conditions and actions for various transitions C. Database Diagrams (20%) Value: 20 Class and ER diagrams describing all data to be stored in the database, along with identifiers and other constraints Workload data (expected number of instances for different classes, frequency of most important operations)

Restructuring of the class diagram Generation of the relational schema Normalization of the schema D. User Interface Design (20%). Covers the design of all user interfaces to be supported by your system. Value: 20% Clear description of the different user groups State diagrams describing the dialogues supported by the interface Mockups of windows Website design (if relevant) Input/Output design Justification that the interface design meets relevant requirements E. Supporting Documentation (10%). Supporting documentation for the selections you made for hardware, software and networking (eg, prices, configurations, vendors considered, ), meetings with your customer (if any), meeting among team members, supporting evidence for some of your design decisions, Value: 10

F. Presentation (10%): The style of your presentation, including language, grammar, clarity, organization of appendices, etc. Value: 10 F1. Language: Deduction of marks for each spelling or grammatical error. Value: 5 F2. Style and clarity: Deduction of marks for each unlabeled figure or point of confusion, or missing style requirement (e.g., table of contents, proper title page, page numbers, introduction, conclusion, etc.). Value: 5