0% found this document useful (0 votes)
90 views

Outcome Assessment Criteria - CSC291: Software Engineering Concepts

Upon completion of the CSC291: Software Engineering Concepts course, students will be able to identify, formulate, and solve software engineering problems; elicit, analyze and specify software requirements; understand core areas of software engineering; function effectively on teams; design, develop, deploy and maintain major software projects; convey technical material orally and in writing; and evaluate solutions to problems in a global society. Assessment methods may include exams, quizzes, assignments, and team-based projects requiring effective interaction and workload sharing.

Uploaded by

junaid
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
90 views

Outcome Assessment Criteria - CSC291: Software Engineering Concepts

Upon completion of the CSC291: Software Engineering Concepts course, students will be able to identify, formulate, and solve software engineering problems; elicit, analyze and specify software requirements; understand core areas of software engineering; function effectively on teams; design, develop, deploy and maintain major software projects; convey technical material orally and in writing; and evaluate solutions to problems in a global society. Assessment methods may include exams, quizzes, assignments, and team-based projects requiring effective interaction and workload sharing.

Uploaded by

junaid
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

Outcome Assessment Criteria – CSC291: Software Engineering Concepts

Upon completion of the subject, students will be able to:

• An ability to identify, formulate, and solve software engineering problems, including the
specification, design, implementation, and testing of software systems that meet
specification, performance, maintenance and quality requirements
• The ability to elicit, analyze and specify software requirements through a productive
working relationship with various stakeholders of the project
• An understanding of the core areas of software engineering
• An ability to function effectively on teams
• The successful design, development, deployment and maintenance of a major software
based projects
• An ability to convey technical material through oral presentation and interaction with an
audience
• An ability to convey technical material through written reports which satisfy accepted
standards for writing style
• An ability to evaluate the impact of potential solutions to software engineering problems
in a global society, using their knowledge of contemporary issues and emerging software
engineering trends, models, tools, and techniques

The following may be useful methods for assessing the success of this course in achieving the
intended outcomes:
• Traditional exams, quizzes, and assignments covering lecture materials generally can be
used for assessment.
• Team-based class activities/projects in which success (i.e., team-based rather than
individually-based grades) requires are effective student interaction and effective work-
load sharing can be useful for assessing success.

Technology:
None

Design skills/techniques practiced:


• First two weeks the students were given lectures related to induction to SE and its real
world applications.
• Every topic covered in class was also practiced in take home assignments and quizzes.

Course analysis:
• Technology:
It’s a course without lab but students are encouraged to use MS Visio, MS Project and
Balsamiq Mockup tools to model the different aspects of their assigned project.
• Emerging Development Paradigms:
Some of the basic assumptions of software development and maintenance paradigms are
changing drastically. For example, software is no more being developed as a product, but
has become a service. This basic paradigm shift is already affecting software developers
as well as the users of software. We first discuss the paradigm shift and the reasons
behind this shift.

• Pertaining to Industry:
Software Engineering is a subject that has fired the imaginations of many. This course is
about working on large, existing, software systems. It focuses on tools, techniques,
practices and principles that software engineers use on a daily basis to successfully build,
modify, maintain and grow the large software systems that form so much of the
infrastructure of trade, commerce, communication and entertainment in the modern
world.

• Modeling and Design:


The model-driven approach to software and systems development proposes to address
quality and complexity issues in the development process. The usage of modeling
languages not only for documentation, but, e.g., for automated analysis, test generation,
and code generation is gaining momentum in particular in the context of (safety) critical
software development. The necessary pre-requisites are a semantically founded modeling
language and methods and tools for analysis. We will take the Unified Modeling
Language (UML) as an example and demonstrate how to equip a relevant sublanguage
(sometimes referred to as executable core) with a precise meaning in line with the official
standard documents.

You might also like