1. SE291 INTRODUCTION TO Software Engineering Spring 2019

2. Instructor Information: Dr. Nada Hany Sherief Office: CCIT 405

3. Learning Objectives Expose students to the software life cycle.
Understand how to analyze, design, implement and test large-scale software.
Practice teamwork in developing software project.
Introduce techniques and standard documents used in each stage of the software life cycle.
Work within a standard development process
Document process and product measurements
Utilize personal design and code reviews effectively
Analyze process data and propose improvements

4. Course Outline Introduction Overview and History of SE
Software Process
Software Process Models
Requirements Engineering
Requirements Definition and Specification
Structured Analysis
OO Analysis
Design Concepts and Principles
Architectural Design
Software Quality Assurance
Verification and Validation

5. Course Book Information
Text Book:
Ian Summerville, ninth Edition, Software Engineering, Addison Wesley.
Web:

6. Grading Policy
All assignments must be submitted on the due date. No late submission is allowed.
Assessment
Method
7th Week (30%)
Exam (20) + Quiz (10)
12th Week (20%)
Project (20)
Coursework (10%)
Assignments (5) + Lecture Attendance (5)
Final (40%)
Examination (40)

7. General Policies
Attendance will be taken every class and will be reported. 
Two late attendances are considered as one absence. 
Official  excuse  for  any  class  absence  must  be  presented  within  one  week  after  that  class. 
No make up exams or quizzes will be given. 
All  grading  issues must  be  resolved  within  a  week  after  the  return  of graded  material. 
Students  are  expected  to  regularly  check  the  course  website  on  aast.edu for  lecture  notes,  updates,  announcements,  etc. 
Participation in the class is strongly encouraged. 
Plagiarism, copying and other anti‐intellectual behavior are prohibited by AASTMT regulations.  Violators will face serious consequences. 

8. Expectation
This course carries 3-credit hours. On the average about 3 hours/week/credit-hour of effort is expected from the student.
The student is expected to interact with the instructor on a frequent basis and review the difficulties he is facing and get the material clarified. Such an effort will bring the student back to the flow of course; otherwise he will lag behind and even the new material will become difficult to follow.
Reading assignments will be given on a regular basis. The student is expected to read the assigned portions in order to gain the most out of the class.

9. What is software engineering?
Software engineering is an engineering discipline that is concerned with all aspects of software production.
Software engineers should adopt a systematic and organised approach to their work and use appropriate tools and techniques depending on the problem to be solved, the development constraints and the resources available.

10. Software Engineering vs. Computer Science
Computer science is concerned with theory and fundamentals; software engineering is concerned with the practicalities of developing and delivering useful software.
Computer science theories are still insufficient to act as a complete underpinning for software engineering (unlike e.g. physics and electrical engineering).

11. Software Engineering vs. System Engineering?
System engineering is concerned with all aspects of computer-based systems development including hardware, software and process engineering. Software engineering is part of this process concerned with developing the software infrastructure, control, applications and databases in the system.
System engineers are involved in system specification, architectural design, integration and deployment.

12. Software Engineer Job Duties
Analyzing user requirements
Testing code, refining and rewriting it as necessary
Researching and designing new software programs
Developing existing programs by analyzing and identifying areas for modification
Integrating existing software products and getting incompatible platforms to work together
Creating technical specifications
Writing operational documentation with technical authors
Maintaining systems by monitoring and correcting software defects

13. Software Engineer Job Duties (contd.)
Working closely with other staff, such as project managers, graphic artists, UX designers, other developers, systems analysts and sales and marketing professionals
Consulting clients and colleagues concerning the maintenance and performance of software systems with a view to writing or modifying current operating systems
Investigating new technologies

14. Employment
Specialist IT firms - such as IT consultancies, large IT providers, software development, internet providers and training firms; organizations that use IT software, systems and equipment, including retailers, law firms, business intelligence and market research organisations, education providers, the armed forces, the public sector and voluntary sector organisations.
Manufacturing industry - including automotive, navigation, telecommunications, manufacturing and construction companies.
Financial services - including global investment banks, financial/banking organisations, security market specialists and the pensions sector.
Public utilities - covering energy and water supply, energy extraction and transport.

15. Tips to the Students
In order to do well in this course the following points are to be noted and considered in your planning:
Your attitude to learn and the effort you put in for this course alone will be the primary agents that guide you in this course.
Taking notes is important. Once you take a note of what you consider to be important bits and pieces of information, write it down in your notes. On the same day after the class, review the relevant material and then prepare detailed notes. Such regular recollection, review, revision, and documentation will turn out to be very important in grasping the material and doing well in quizzes and examinations.
Regular interaction during the class & during the instructor's office hours is encouraged. There is nothing like a silly question. By raising doubts and posing questions, you will be helping yourself, others in the class, and the instructor in steering the coverage towards the weak points. So keep one thing in mind during this course: “ it is better to raise a doubt or pose a question, rather than suppressing it and face difficulties later on.

16. Tips to the Students (contd.)
If you do not follow the instructor's pace/language, request him to slow down. Likewise, when you do not understand certain words or sentences request for an alternative explanation.
Reading and written assignments as well as quizzes, projects & examinations are part and parcel of the course. They are expected to supplement the coverage in the class/lab. So treat them that way instead of facing them just as tests for evaluating your performance.
There is no substitute for a regular (daily) preparation for this course. It will be far less effective, even if you spend two times more effort just before the examination days.
Good luck and best wishes for a good semester 