THE DILEMMA BETWEEN SOFTWARE ENGINEERING AND SYSTEMS ANALYSIS & DESIGN MOHAMMAD A. ROB MANAGEMENT INFORMATION SYSTEMS UNIVERSITY OF HOUSTON-CLEAR LAKE HOUSTON, TEXAS

PRESENTATION OUTLINE  INTRODUCTION  METHODOLOGY  RESULTS  The Convergence and Divergence  5QMMs: Five Quality Management Metrics in SE  CONCLUSION 2 THE DILEMMA BETWEEN SA&D AND SE

TOO MANY BOOKS IN SYSTEMS ANALYSIS & DESIGN 3 THE DILEMMA BETWEEN SA&D AND SE

NOT TOO MANY TEXT BOOKS ON SOFTWARE ENGINEERING 4 THE DILEMMA BETWEEN SA&D AND SE

BUT THERE ARE MANY OTHER BOOKS IN THE SE PROGRAM 5 THE DILEMMA BETWEEN SA&D AND SE

SOFTWARE ENGINEERING COURSES  REQUIREMENTS ENGINEERING  SOFTWARE ARCHITECTURE & DESIGN  SOFTWARE CONSTRUCTION  SOFTWARE TESTING  SOFTWARE MAINTENANCE  SOFTWARE CONFIGURATION MANAGEMENT  SOFTWARE ENGINEERING MANAGEMENT  SOFTWARE ENGINEERING PROCESS  SOFTWARE ENGINEERING TOOLS AND METHOD  SOFTWARE QUALITY MANAGEMENT 6 THE DILEMMA BETWEEN SA&D AND SE

INTRODUCTION  ONE COURSE IS TAUGHT ON SYSTEMS ANALYSIS & DESIGN IN THE MIS PROGRAM.  SOFTWARE ENGINEERING COULD BE A SINGLE COURSE OR A PROGRAM WITH MULTIPLE COURSES.  BOTH ARE FOCUSED TO DEVELOP A SYSTEM OR A SOFTWARE; AND SOFTWARE IS PART OF A SYSTEM.  SO WHAT ARE COMMONALITIES AND WHAT THE DIFFERENCES? 7 THE DILEMMA BETWEEN SA&D AND SE

METHODOLOGY  TWO LEADING TEXTBOOKS FROM TWO SUBJECT AREAS ARE COMPARED CHAPTER BY CHAPTER AND TOPIC BY TOPIC. 8 THE DILEMMA BETWEEN SA&D AND SE TOPICPRESSMANDENNIS & Wixom Process Models Text Organization Project Management OO Design CMM, ISO 9000, Six Sigma Function Points, COCOMO

METHODOLOGY  OTHER SA&D TEXTS ARE ADDED TO CHECK THE COVERAGE OF VARIOUS TOPICS 9 THE DILEMMA BETWEEN SA&D AND SE TOPICPRESSMANDENNIS & Wixom KENDAL & KENDALL Satzinger Process Model xxxx Text Organization HolisticWaterfallHolisticWaterfall Project Management xxxx OO Design xxsome CMM, ISO 9000, Six Sigma xsome Function Points, COCOMO xx--

RESULTS: CONVERGENCE AND DIVERGENCE 10 THE DILEMMA BETWEEN SA&D AND SE Systems Analysis & DesignSoftware Engineering  Process Models are same  Origin of the models are in SE  Traditionally deals with the development of business information system including software, hardware, database, network, and user interface.  Traditionally deals with the development of complex, technical, mission critical, real-time, and embedded software in all domains.  Only one course in the Management Information Systems program.  A course or a whole program with many courses in a Software Engineering program.

RESULTS: CONVERGENCE AND DIVERGENCE 11 THE DILEMMA BETWEEN SA&D AND SE Systems Analysis & DesignSoftware Engineering  Clearly prepares a Systems Analyst.  Not clearly mentioned, but it prepares a Software Engineer or Software Architect.  Most textbooks are highly organized according to the phases and activities of SDLC Waterfall model, but some are taking an approach like Software Engineering.  Most textbooks take a holistic approach in organizing chapters in the textbooks.

RESULTS: CONVERGENCE AND DIVERGENCE 12 THE DILEMMA BETWEEN SA&D AND SE Systems Analysis & DesignSoftware Engineering  Focused on the Systems Development Life Cycle (SDLC). Newer editions bring many quality issues like CMM, ISO and Six Sigma.  Focused on the Software Quality and Project Management.  There is at least one chapter on Project Management.  There are multiple chapters on Project Management.

RESULTS: CONVERGENCE AND DIVERGENCE 13 THE DILEMMA BETWEEN SA&D AND SE Systems Analysis & DesignSoftware Engineering  Software Engineering concepts like COCOMO, Function Points, Use Case, UML, OO design, Quality Assurance are being included in recent editions.  Business and web-based systems are being added to adapt to the changing need of the market.  May fit into the CMM Level 3, as project management and SDLC models are discussed elaborately.  Can fit into CMM level 2 and higher depending on how many KPAs are discussed.

RESULTS: THE QUALITY FOCUS IN SOFTWARE ENGINEERING  QUALITY IS THE MAIN FOCUS IN SOFTWARE ENGINEERING 14 THE DILEMMA BETWEEN SA&D AND SE

RESULTS: 5 QUALITY MANAGEMENT METRICS IN SE  SOFTWARE QUALITY MANAGEMENT  SOFTWARE PROJECT MANAGEMENT  (COMMON FOR MIS AND SE PROGRAM)  SOFTWARE REQUIREMENTS MANAGEMENT  SOFTWARE RISK MANAGEMENT  SOFTWARE CONFIGURATION MANAGEMENT 15 THE DILEMMA BETWEEN SA&D AND SE

CONCLUSION  OUR ANALYSIS SHOWS THAT THE “QUALITY” FOCUS IS THE KEY FACTOR IN THE AREA OF SOFTWARE ENGINEERING, WHILE THE PROCESS MODELS AND BASIC PROJECT MANAGEMENT ACTIVITIES ARE THE SAME IN BOTH SUBJECTS.  IN ADDITION TO SELECTING A PROCESS MODEL, A SOFTWARE ENGINEER TYPICALLY FOCUSES ON FIVE QUALITY MANAGEMENT METRICS (5QMMS) TO DEVELOP A QUALITY SOFTWARE.  MANY SOFTWARE ENGINEERING CONCEPTS ARE BEING ADAPTED TO THE SYSTEMS ANALYSIS & DESIGN TEXTS. 16 THE DILEMMA BETWEEN SA&D AND SE

CONCLUSION  TODAY’S SOFTWARE MARKET IS DOMINATED BY LARGE BUSINESS AND WEB-BASED SYSTEMS RATHER THAN TRADITIONAL TECHNICAL AND GOVERNMENTAL SYSTEMS.  WHETHER OR NOT SOFTWARE DEVELOPMENT IS AN ENGINEERING PROCESS MAY STILL BE A DEBATABLE ISSUE, BUT WITH THE PROGRESSION OF TIME, THE FIELDS OF SA&D AND SE ARE CONVERGING CLOSER TO EACH OTHER.  THEIR DISTINCTIONS ARE BEGINNING TO BLUR, NOT DUE TO ENGINEERING OR BUSINESS PER SE, BUT SUBSEQUENT TO THE WHIM OF CHANGING MARKET DEMANDS.  SOFTWARE ENGINEERING TEXTS SHOULD CONTINUE TO ADDRESS THE TOPICS THAT RELATE TO LARGE BUSINESS SYSTEMS INCLUDING DATABASE AND WEB TECHNOLOGIES. 17 THE DILEMMA BETWEEN SA&D AND SE