paper

IST 603, Systems Analysis Methods

CLEVELAND STATE UNIVERSITY

Monte Ahuja College of Business Administration

Department of Information Systems

IST 603 Systems Analysis Methods

Final Project – Fall 2021

2 Presentations + 1 Report

Grade: 20% of your final grade

Description: The goal of this final project is to have students work as a team (previously formed) and demonstrate their ability to develop a system Specification including analysis, design, project plan and schedule. Additional credit will be given for system interface design and a functional prototype. Each team must select a topic, develop system models as required at the end of the semester using the tool or tools you choose.

Each team will need to gain my approval to work on your final project to ensure the scope of the project is appropriate for one semester. I strongly recommend each team to schedule an appointment with me either in person or Zoom to discuss the topic and final project before your proposal presentation.

The final project includes three phases that require students to master systems analysis & design skills in different modules. I expect students to work as teams and each team member must actively participate in final project activities.

Present your project using one of the following two options: 1) Zoom by appointment, or 2) in person on a Thursday by appointment. Since there are not that many Thursdays before the proposal presentation, you may have to choose Zoom.

· 9/27-10/1 Proposal Presentation. Phase I (System Planning): Select a topic and develop project description, analyze the business case, and project management.

· Phase II (Systems Analysis/Design): requirements, models as appropriate. Update your current progress of your project. Project feedback requests can be scheduled anytime within reasons.

· 11/29 – 12/3 Final Project Presentation.

· Peer-evaluation: (Lower ratings may lead to a lower grade to your final project.)

· The presentation may include a project overview, walk-through of model, design, and outcome. Each team member must participate/present in the class presentation. The length of the presentation is 10-15 minutes. Failure to present your final project will be penalized by at least 15% of the overall Project score.

Group Policy: It is highly likely that your team members are not active or not even taking part in the final project. However, this is NOT a legitimate reason for you not to turn in your final project on time. If you do care about your grade and project, find a solution for this situation. In fact, the team project also can be done individually. I list the policies:

1. You will work on the same team

2. Students might opt out of a team. In that event, the student will be responsible for the entire project by himself or herself without reduction in scope of the project. Any opt out has to be preapproved by me latest by October 4, 2021.

3. There is no free ride for the final project. Each team member must make equal contributions to the final project.

4. Failure to take part in team discussions/meetings may cause a zero point of your case projects toward your final grade.

5. A self/peer evaluation will be used to grade the case projects.

Deliverables for the final, complete project:

The presentation should include the following components:

1. Introduction: purpose of the project, strategic planning, business case, system requests, and feasibility study

2. Project Overview: Task patterns, critical path, software tools, risk management

3. Current Application/System: Include a high-level diagrams and descriptions of the current system. Include current business process, current problems and issues.

4. Systems Analysis: DFDs, Use Case, Sequence, State Transition, Activity, Business Process Modeling, etc. (At least 5 different diagrams are required.)

a. UML: https://www.uml-diagrams.org/

b. Lucidchart: https://www.lucidchart.com/blog/types-of-UML-diagrams

5. Optional component - User Experience Design: Use design principles or a pilot study to enhance your design.

a. You may have a live system, web pages, mobile app, or even a prototype. The instructor may introduce some options and you may choose your own.

6. Conclusion: Summarize the information about the system design and potential benefits.

Each team will need to submit the final project to BB as a group including the following components:

1. Final Report + Presentation PPT

Each student will need to submit a peer evaluation to BB independently.

Final Project and Report Rubric

Objective	Trait	Deficient (1…2)	Competent (3…4)	Exemplary (5…6)	Score
Graduates can write professional quality documents	Introduction	Opening not appropriate to message purpose; not concise; no clarity of purpose.	Opening appropriate to message; clear and concise purpose.	Opening is clear, concise and considerate; sets tone.
	Organization	Disorganized; incorrect format; unclear direction.	Organized; correct format; clarity of main points.	Clear, considerate, correct formatting and development of main points.
	Content	Incorrect; irrelevant; no concrete (supporting) evidence.	Relevant and correct with concrete (supporting) evidence.	Relevant; correct; complete; incorporates innovative insights.
	Conclusion	Missing or content does not support conclusion.	Supports content; contains summary statement.	Clear; complete; closing is courteous (close on a positive thought/audience consideration).
	Grammar & Spelling	Numerous errors in grammar and spelling.	Minimal errors in grammar and spelling but does not detract from readability.	No errors in grammar and spelling.
	APA Style	Numerous errors in APA Style (not citing sources correctly, formatting issues, etc.)	Minimal errors in APA Style but does not detract from readability.	No errors in APA Style.

Grading Rubrics: Your final score will be based on the following rubric:

Rubrics	Description	You will receive
5 - 6	Your case studies meet the most requirements specified above.	90 - 100 % of your scores
3 – 4	Your case studies meet the partial requirements specified above.	70 - 89 % of your scores
< 3	Your case studies do not meet the requirements specified above.	< 70 % of your scores

Peer Review Rubric

Description: Teamwork is imperative for any team projects. Most course work and work environments involve team work. In this course, students work in teams. Each student contributes his/her limited, precious time to complete the assigned project and class activities. It is very important that you share the responsibilities and make significant contributions to the project.

Objectives:

1. Graduates can demonstrate appropriate team techniques to participate in a team task that results in effective performance.

2. Graduates can demonstrate effective leadership skills in a team project.

Traits:

The rubric is used to measure the following traits: attendance, preparation, contribution, positive attitude, motivation, conflict resolution, and accountability.

This rubric will be used for any team activities, e.g., case studies and in-class activities.

Scale:

Scale	Description List
4- 5 Excellent	· Attend team meetings most of the time. · Come well prepared, e.g., data collection, paper work, Ideas, etc. most of the time. · Clearly contribute to team activities, e.g., design pages, debug code, prepare the documents/PowerPoint, conduct testing, usability test, provides ideas, etc. · Contribute a fair amount of time to team activities. · Frequently volunteers to take responsibility for team tasks. · Frequently encourage peers, motivate peers, communicate with peers with mutual respect, even conflicts and disagreement occur.
3 - 4 Average -Good	· Miss meetings a few times with legitimate reasons. · Come with some preparations, e.g., data collection, paper work, Ideas, etc. at times. · Clearly contribute to team activities, e.g., design data models, prepare the documents/PowerPoint, prepare in-class discussion material, provides ideas, etc. · Find excuses at times, but still take his/her responsibility for team activities. · Normally volunteers to take responsibility for team tasks. · Occasionally encourage peers, motivate peers, communicate with peers with mutual respect, even conflicts and disagreement occur.
< 3 Poor	· Miss most of meetings. · Come with limited or no preparations. · Limited or no clear contributions. Other team members have to do extra work to cover his/her slack work. · Find excuses most of the time to team activities. · Rarely volunteer to take responsibility for team tasks. · Rarely encourage peers, motivate peers, communicate with peers with mutual respect, even conflicts and disagreement occur.
0 No Show	· The member never shows up in meetings and does nothing to team activities.

Grading Rubrics: Your final score will be based on the following rubric:

Rubrics	You will receive
4 - 5	90 - 100 % of your scores
3 – 4	70 - 89 % of your scores
< 3	< 70 % of your scores