This applied course on Software Engineering topic may be considered as a second course on Software Engineering; After taking at least one of the courses “System Analysis & HCI Design” or “Software Enginneering”, this course will lead from detailed software design to software acceptance test; While student living in the medium applied measurements on productivity, error per KDSI, etc will be measured by the student..
Prerequisite(s)
-
Corequisite(s)
-
Special Requisite(s)
-
Instructor(s)
Instructor Mehmet DEMİR
Course Assistant(s)
-
Schedule
The course is not opened for this semester.
Office Hour(s)
The course is not opened for this semester.
Teaching Methods and Techniques
-
Principle Sources
A) Ian Sommerville; Software Engineering; Pearson 2011; 9th printing; ISBN 978-0-13-705346-9 B) Shari L. Pfleeger & Joanne M. Atlee ; Software Engineering; Pearson 2010 ; fourth edition ; ISBN 978-0-13-814181-3
C) Hans van Vliet ; Software Engineering : Principles and Practice ; john wiley 2000; second printing ; ISBN 0-471-97508-7
Other Sources
-
Course Schedules
Week
Contents
Learning Methods
1. Week
Detailed Software Design;
Students must have a good “system analysis report” from their previous (prerequisite) course; these will be reduced for competition that have at least two sides
2. Week
Frequently used application area standards (ieee, iso, DoD, ..),
Start your detailed design on your group project
3. Week
Decomposition & modularization; coupling and cohesion; information hiding ;
Project groups will search for their application area standards
4. Week
information hiding
Decompose the required software into modules that will minimize information flow between components
5. Week
DB table design and Component design
Parallel development and modification to lecture part of the course
6. Week
Software Construction – top down and bottom up methods at the beginning; selection of the method planning for temporary driver routines
Parallel development and modification to lecture part of the course
7. Week
software construction standards for hypothetical CMMI level3 firm
Parallel development and modification to lecture part of the course
8. Week
Most probably time for midterm exam
Parallel development and modification to lecture part of the course
9. Week
anticipating chance – risk identification, risk probability estimation, consequences of the risk; plan for most possible changes
Parallel development and modification to lecture part of the course
10. Week
Software Testing ( unit test, component test, version management; configuration management );
Parallel development and modification to lecture part of the course
11. Week
Managing software construction – human related problems and risks
Parallel development and modification to lecture part of the course
12. Week
internal memo system of the software firm ( evolving tools for the environment) ; integration test; alpha test; beta test and acceptance test preparation in 4LSE;
Parallel development and modification to lecture part of the course
13. Week
Software Measurement units and tools;
Parallel development and modification to lecture part of the course
14. Week
measuring the software and programmer productivity that has been developed
Parallel development and modification to lecture part of the course
15. Week
16. Week
17. Week
Assessments
Evaluation tools
Quantity
Weight(%)
Midterm(s)
1
27
Attendance
1
6
Laboratory
1
27
Final Exam
1
40
Program Outcomes
PO-1
Adequate knowledge in mathematics, science and engineering subjects pertaining to the relevant discipline; ability to use theoretical and applied information in these areas to model and solve engineering problems.
PO-2
Ability to identify, formulate, and solve complex engineering problems; ability to select and apply proper analysis and modelling methods for this purpose.
PO-3
Ability to design a complex system, process, device or product under realistic constraints and conditions, in such a way so as to meet the desired result; ability to apply modern design methods for this purpose. (Realistic constraints and conditions may include factors such as economic and environmental issues, sustainability, manufacturability, ethics, health, safety issues, and social and political issues according to the nature of the design.)
PO-4
Ability to devise, select, and use modern techniques and tools needed for engineering practice; ability to employ information technologies effectively.
PO-5
Ability to design and conduct experiments, gather data, analyse and interpret results for investigating engineering problems.
PO-6
Ability to work efficiently in intra-disciplinary and multi-disciplinary teams; ability to work individually.
PO-7
Ability to communicate effectively, both orally and in writing; knowledge of a minimum of one foreign language.
PO-8
Recognition of the need for lifelong learning; ability to access information, to follow developments in science and technology, and to continue to educate him/herself.
PO-9
Awareness of professional and ethical responsibility.
PO-10
Information about business life practices such as project management, risk management, and change management; awareness of entrepreneurship, innovation, and sustainable development.
PO-11
Knowledge about contemporary issues and the global and societal effects of engineering practices on health, environment, and safety; awareness of the legal consequences of engineering solutions.
Learning Outcomes
LO-1
This applied course on Software Engineering topic may be considered as a second course on Software Engineering; After taking at least one of the courses “System Analysis & HCI Design†or “Software Enginneeringâ€Â, this course will lead from detailed software design to software acceptance test; While student living in the medium applied measurements on productivity, error per KDSI, etc will be measured by the student..
