Introduction to CSE 757

1. Introduction to CSE 757 • Course Info • Syllabus, Schedule • Norms and Expectations • Get started!

2. Course Description • Principles of design, implementation, validation, and management of computer software; emphasis on reading and discussing papers from relevant journals and proceedings.

3. Course Objectives • Study and understand the scope of software engineering issues, techniques, methodologies and technologies  • Especially for Enterprise Software Systems • Large-scale systems that support large industry and government organizations • Frameworks for each component of enterprise software engineering

4. Section Information • Class Meets: MWF@12:30-1:18, DL266 • Course Site: http://carmen.osu.edu • Credit:  3 UG/G credit hours • Prerequisite:  CSE 560 and senior standing or graduate student

5. Lecturer Information • Bettina Bair (bbair@cse.osu.edu) • Office: DL493 • Office Hours: MW@3:00, T@11:30, F@1:30 • Grader: David Kitchener, kitchener.1@buckeyemail.osu.edu

6. My Background • 18 Years in industry • Department of defense, telecom, intelligence • Systems analyst, manager, software engineer • Databases, billing services, capacity planning • 10 years in academia • Curriculum development and teaching • Architecture, business, statistics, human resources, systems analysis, computer aided problem solving, operating systems… • About 5 years consulting and self-owned business • Service architecture, web development

7. Frameworks • Mechanism for monitoring the field of action • A way of remembering what results are desired • A means of comparing what is perceived against what is desired • A record of a set of components for taking action when there is a difference • In computer science, frameworks can be based on a variety of representational tools • Patterns • Best practice processes • Templates • Ontologies

8. Course topics are as follows: • Analytic frameworks for understanding the business and the relationship between the business and information technology. • Topics will include: • Business Strategy • Innovation • Business-IT Alignment • Enterprise Architecture • Fundamentals of software engineering – software engineering methodologies for requirements, analysis, architecture, design, implementation and testing, and project management.

9. Topics include frameworks for: • Requirements and analysis • Architecting software systems • Software design • Object-oriented design & Patterns • Human-computer interface design • Software Project Management • Software estimation • Software and system maintenance • ITIL and infrastructure management • Special topics • Open Source software • Product-line engineering, model-driven architecture, and software factories

10. Method • Inside – Out • Read material in advance of class, in order to fully participate in class discussion • Complete short quizzes on assigned papers. • Identify a Software Engineering professional to interview about course topics. • Present a summary of that interview in class.

11. Grades • Class participation: 12% • Mini-quizzes: 30% • Presentation Proposal – Parts A & B: 8% (2 @ 4% each) • Presentation Evaluation by Peers: 4% • Presentation Evaluation by Instructor: 16% • Final: 30% (must pass final, to pass course) 

12. Readings Applying UML and Patterns – An Introduction to Object Oriented Analysis and Design, Craig Larman Balancing Agility and Discipline, Boehm Beyond Stereotypes Of IT Professionals, Harvey G. Enns, Thomas W. Ferratt, And Jayesh Prasad Business IT Alignment: Then and Now, Holland, Skarke Business Patterns, Adrian Slywotzky Component Business Models – Making Specialization Real, IBM Institute for Business Value Disruptive Innovation In Health Care Delivery: A Framework For Business-Model Innovation, Jason Hwang and Clayton M. Christensen From “Make and Sell” to “Sense and Respond,” Stephen J. Haeckel, IBM How Competitive Forces Shape Strategy, Michael Porter How information gives you competitive advantage, Porter IBM OOTC book IT Alignment: What we have learned, Chan, Reich IT-enabled sense-and-respond strategies, Ramnath, Landsbergen Meeting the Challenge of Disruptive Change, Clayton M. Christensen and Michael Overdorf Patterns of Enterprise Application Architecture, Martin Fowler et. al Services Science – a new field for today’s economy, Paulson Simple guide to EA, Bailey Software Architecture In Practice, Len Bass et. al., Safari Software Engineering By Shari Lawrence Pfleeger, Joanne M. Atlee Stage-Gate systems: a new tool for managing new products - conceptual and operational model, Cooper The eXtreme Programming (XP) Metaphor and Software Architecture, Herbsleb, CMU Technical Report UML Distilled, Martin Fowler Use Case Points – An Estimation Approach Using the Balanced Scorecard as a Strategic Management System, Kaplan and Norton Visual Studio Team System: Better Software Development for Agile Teams, Will Stott; James W. Newkirk Waltzing with Bears - Managing Risks on Software Projects, Tom DeMarco, Timothy Lister

13. Readings en.wikipedia.org/wiki/Agile_software_development en.wikipedia.org/wiki/Extreme_Programming_Practices en.wikipedia.org/wiki/Requirements_analysis en.wikipedia.org/wiki/Delphi_method en.wikipedia.org/wiki/Wideband_delphi www.agilemodeling.com/essays/agileRequirements.htm www.research.ibm.com/ssme/ www.roughtype.com/archives/2007/01/it_doesnt_matte.php www.sandhill.com/opinion/editorial_print.php?id=129 www.tcs.com/SiteCollectionDocuments/White%20Papers/DEWP_05.pdf

14. Online research sites include: • Safari Text Books Online:  • http://library.ohio-state.edu/search/y?SEARCH=Safari • Business Source Complete:  • http://library.ohio-state.edu/record=e1000557 • ACM Digital Library:  • http://library.ohio-state.edu/record=e1000050 • IEEE Explore:  • http://library.ohio-state.edu/record=e1000005

15. Norms and Expectations • Attendance • Required at all classroom sessions and team meetings. • Quizzes and reviews will be collected each session. • There will be no make-up exams, presentations, lectures, etc. • ClassPreparation • Read the assigned material • Be prepared to answer study questions and participate in discussion

16. Norms and Expectations • Assignments:  • Due—in typed hardcopy—at the beginning of class on the due date. • Contact and class information:  • Carmen will be extensively used for the dissemination of material, announcements, asynchronous discussion and possibly submission of assignments. • Sharing and attribution of intellectual property and information:  • You may freely research and use information legally available from the Web or other sources. • However, you must properly attribute each piece of borrowed intellectual property.

17. Carmen • Big news and announcements • Download articles and forms • Gradebook • Asynchronous Discussion • More?

18. To Do • By the next class • Look over the Carmen site and find Schedule, Readings, Forms and the Discussion board • Find the INTRODUCTION form and complete it.  Bring it to the next class. • Look at the assigned reading for the next class period.  Make sure that you can summarize the articles and answer all of the study questions.

19. To Do • This week • Locate all of the readings for this quarter.   • Some are posted on Carmen, some are available as webpages and some will have to be downloaded from a library site, like Safari. • Look for a software engineering company where there might be professionals for you to interview. • On Monday • Turn in your Project Proposal - Part A

20. Find a Professional to Interview • Interviews and presentations will be scheduled throughout the quarter. • Interview guidelines • About 1 hour, on a particular topic and assigned reading • Face-to-face preferred • Present a summary to class

21. Interview Summary Structure • Company Name, Description, products/services offered • Reason selected • Interviewee name, title, job description • Questions & Answers • References

22. Interview Summary Evaluation Organization – • Well –prepared? • Topics and main points outlined? • Stayed on topic? • Smooth transitions? • Main points summarized? Content – • Information complete? • Accurate? • Provided a new perspective of material already discussed? Relevancy – • Information relevant to the assigned topic? • Presenters connected new ideas to topic using references? Communication – • Easy to understand? • Effective use of visual aids? • Clear and at a level appropriate to the audience? • Made good use of the available time? Participation – • Team members contributed equally to the presentation? • Presenters treated each other professionally and with respect

23. Software Engineering Professionals • Where are they? • How do you contact them? • How do you arrange an interview?

24. Assigned Reading & Questions • WWW: • www.sandhill.com/opinion/editorial_print.php?id=129 • www.roughtype.com/archives/2007/01/it_doesnt_matte.php • www.research.ibm.com/ssme/ • www.tcs.com/SiteCollectionDocuments/White%20Papers/DEWP_05.pdf • Carmen: • Beyond Stereotypes Of IT Professionals, Enns, (p105-enns.pdf) • What is SaaS? • Why doesn’t IT matter? • What is SSME? • What are the IT personality stereotypes? • What are the three pillars of delivery excellence?