This site also links to additional resources, real world examples, and articles related to many topics in the book. It provides resources for both students and instructors. New to This Edition. Chapters 5 and 6 in the new edition now provide significant, concrete advice on how to approach a design problem on two levels: System Level — Chapter 5 has been significantly revised to focus just on architectural design: In addition to architectural styles which were in the third edition , the new chapter includes architectural views and advice on combining views, tactics for revising an architecture to improve quality attributes, and software product lines.
Prediction Share a link to All Resources. Instructor Resources. About the Author s. Previous editions. Software Engineering, 3rd Edition. Relevant Courses. Software Engineering -- Introduction Computer Science. Sign In We're sorry! Username Password Forgot your username or password? Sign Up Already have an access code? Instructor resource file download The work is protected by local and international copyright laws and is provided solely for the use of instructors in teaching their courses and assessing student learning.
Signed out You have successfully signed out and will be required to sign back in should you need to download more resources. All assignment submissions are through Moodle. The submission deadlines are sharp and the submission site will be closed at the specified time. We understand that circumstances may arise where you may need to miss a class, or submit an assignment late. Medical conditions, religious or funerary events, university-related events conference visit, athletic event, field trip, or performance , or extenuating non-academic reasons military obligation, family illness, jury duty, automobile collision that need extension will be accommodated with written documentation.
Your success in this class is important to us. All assignments must be completed to pass this course. The final numerical cutoff for final course letter grade assignment will be made after all grading is done.
Incompletes will be granted only in exceptional cases, and only if you have completed at least half the course with a passing grade. Prior to that, withdrawal is the recommended course of action. Software engineering is at its nature a collaborative activity and it benefits greatly from diversity.
We celebrate the diversity in our community and actively seek to include and listen to voices that are often silenced in the computing world. We welcome all individuals regardless of age, background, citizenship, disability, sex, education, ethnicity, family status, gender, gender identity, geographical origin, language, military experience, political views, race, religion, sexual orientation, socioeconomic status, and work experience. Everyone has the right to be addressed by the name and pronouns that they use for themselves.
I am committed to ensuring that I address you with your chosen name and pronouns. Let me know what name and pronouns I should use for you if they are not on the roster. Please remember: We want to foster open discussion in this course. Any kind of language or action displaying bias against or discriminating against members of any group, or making members of any group uncomfortable are against the mission of this course and will not be tolerated. The instructor welcomes discussion of this policy, and encourages anyone experiencing concerns to speak with her.
Students are allowed to work together on all aspects of this class. When the work is individual, we expect that you will complete the work on your own. Whenever students use Internet, literature, and other publicly-available resources, they must clearly reference the materials in their write ups, attributing proper credit. This cannot be emphasized enough: attribute proper credit to your sources.
Failure to do so will result in a zero grade for the assignment and possibly a failing grade for the class, at the instructor's discretion. Copying directly from resources is not permitted, unless the copying is clearly identified as a quote from a source. Most use of references should be written in the words of the student, placing the related work in proper context and describing the relevant comparison.
These policies and guidelines apply to this class. Students who violate University standards of academic integrity are subject to disciplinary sanctions, including failure in the course and suspension from the university.
Since dishonesty in any form harms the individual, other students, and the university, policies on academic integrity have been and will be strictly enforced.
The following text books provide a more comprehensive discussion of the topics addressed in this class. Note that these text books are not a requirement for this class. Students should have taken an intermediate course in software engineering and have built, in a team, a software system of roughly 10, lines of code or more.
The ability to use linux and download and use off-the-shelf tools are expected. Thank you. Course introduction. Software architecture and design. Best and worst programming practices. Object oriented design principles. Object oriented design patterns. User interfaces. Version control. In-class exercise: Advanced uses of git.
0コメント