SDEV-230: Info Systems Analysis & Design
January 26, 2021 2021-01-26 10:15SDEV-230: Info Systems Analysis & Design
SDEV-230: Info Systems Analysis & Design
This course is intended to provide comprehensive, balanced and up-to-date coverage of systems analysis and design. The course maintains the dual focus on the concepts and techniques from both the traditional, structured approach and the object-oriented approach to systems development. Project management, teamwork and presentation skills are also emphasized. Student learning is reinforced through discussions and assignments.
This course is intended for anyone who is involved in developing software system requirements and architectures (e.g., users, technical managers, product managers, technical leads, other software project team members, and clients).
There are no prerequisites for this course. However, it is strongly recommended that students have some familiarity with software development practices and programming concepts. In addition, students should have access to and a moderate level of proficiency with desktop applications such as MS Word, MS Excel and MS PowerPoint or their open source equivalents. Drawing and diagramming software, like MS Visio or its open source equivalent, may also be useful.
Prerequisites: CMIT-135: Intro to Computer Systems -AND- CMIT-200: Relational DB Design & SQL
|
|
Modern Systems Analysis and Design, 8th Edition
|
- Students should have access to and be proficient with a common word processing program such as OpenOffice Writer or MS Word.
- For the design portions of the course, students may be required to use a drawing or modeling tool, such as OpenOffice Draw or MS Visio. Other programs in an office suite may be used for these drawings as well. Alternatively, students may hand draw these diagrams IF they have the ability to submit the assignment as a pdf file.
At the end of this course students will have assembled enough information to help them:
- Understand the project selection process and how it relates to business strategy.
- Understand both traditional, iterative, accelerated and object-oriented methodologies and know when to apply each.
- Apply the basic principles of project management.
- Plan and initiate an information systems project.
- Determine and clearly represent systems requirements.
- Design a database and required interfaces and outputs.
- Plan for implementation and post-project maintenance of a system.
| Week (#) | Topics (Outcomes)1 |
| Week 1
|
Foundations for System Development
a. The Systems Environment (1)1 |
| Week 2
|
Project Selection & Planning
a. Identifying and Selecting Systems Projects (1,2,3)1
b. Initiating and Planning the Project (3,4)1 |
| Week 3
|
Analysis – Process Requirements
a. Determining System Requirements (5)1
b. Structuring System Process Requirements (5)1 |
| Week 4
|
Analysis – Data Requirements
a. Structuring System Data Requirements (5,6)1
Mid-Term Exam |
| Week 5
|
Design – Database and Interfaces
a. Designing Databases (5,6)1
b. Designing Forms and Reports (5)1 c. Designing Interfaces (5)1 |
| Week 6
|
Design – Distributed Systems
a. Distributed and Internet Systems (5,6,7)1
|
| Week 7
|
Implementation and Maintenance
a. Strategies for Implementation (3,7)1
b. Maintaining the System (3,7)1 Final Exam |
1See Student Centered Learning Outcomes in the Syllabus.
| Graded Elements | Percentage |
| Homework | 35% |
| Midterm | 15% |
| Discussion | 35% |
| Final Exam | 15% |
| Total | 100% |
| Extra Credit Course Feedback Discussion | 1% |
| Extra Credit: IDEA Survey | 1% |
| Criteria | Description | Max Points |
| Frequency | Distributes participation across 3-4 days throughout the week creating a dialogue. | 20 |
| Initial Discussion Posting | Posts well developed, timely discussions that fully address and develop all aspects of the task. | 20 |
| Follow-up Postings | Demonstrates timely analysis of others’ posts; extends meaningful discussion by building on previous posts. | 20 |
| Content Contributions | Posts factually correct, reflective and substantive contributions; advances discussion. | 20 |
| Reference & Support | Uses references to literature, readings, or personal experience to support comments. | 20 |
| Total Points: 100 |
Grading Policy
CPS grading and late policies (Links to an external site.)
| Student Resources & Policies Homepage | |
| Academic Honesty | Accessibility and Accommodations |
| Grading Scale | Student Resources |
| Library Resources | Writing Center Information |
| Smarthinking Online Tutoring | Academic Coaching |
Course summary:
| Date |
Details |
|
|---|---|---|
| Sun, 19 Mar 2017 | Assignment Week 1: Discussion Choice (Graded) | due by 23:55 |
| Assignment Week 1: Introductions (Graded) | due by 23:55 | |
| Assignment Week 1: Project Management Charts and Tools | due by 23:55 | |
| Assignment Week 1: Project Methodology | due by 23:55 | |
| Sun, 26 Mar 2017 | Assignment Week 2: Discussion Choice (Graded) | due by 23:55 |
| Assignment Week 2: Project Benefits & Risks | due by 23:55 | |
| Sun, 2 Apr 2017 | Assignment Week 3: Discussion Choice (Graded) | due by 23:55 |
| Assignment Week 3: Documenting and Diagramming Requirements | due by 23:55 | |
| Sun, 9 Apr 2017 | Assignment Week 4: Designing Security (Graded) | due by 23:55 |
| Assignment Week 4: Mid-Term Part II (In-Depth) | due by 23:55 | |
| Assignment Extra Credit Course Feedback Discussion | due by 23:59 | |
| Assignment Week 4: Mid-Term Part I (Timed) | due by 23:59 | |
| Sun, 16 Apr 2017 | Assignment Week 5: Database Design | due by 23:55 |
| Assignment Week 5: Database Normalization (Graded) | due by 23:55 | |
| Sun, 23 Apr 2017 | Assignment Week 6: Project Usability (Graded) | due by 23:55 |
| Assignment Week 6: Representing Scenarios and System Interactions | due by 23:55 | |
| Fri, 28 Apr 2017 | Assignment Week 7: Course Reflection & Close Out (Graded) | due by 23:55 |
| Assignment Week 7: Project Best Practices | due by 23:55 | |
| Assignment Extra Credit: IDEA Survey Quiz | due by 23:59 | |
| Assignment Week 7: Final Exam | due by 23:59 | |
