Lecture Notes On Collaborative Software – Alejandra J Magana (1)

To clarify the distinction between requirements and user stories, I have in bold the requirements in Figure 3.7. Additionally, I only extended two requirements, Number 1 and Number 3, but each of the 10 requirements presented in Figure 3.6 should be expanded into a collection of user stories. 3.1.4 The Workplan A critical role of a product owner (or a project manager) is to plan, con- trol, and assign resources for the development of a system within a speci- fied time frame at a minimum cost with the right functionality.

A common tool that assists project managers in performing this critical role is by means of a work plan. A work plan is a dynamic schedule that records and keeps track of all the tasks that need to be accomplished over the course Figure 3.7. A partial product backlog with requirement numbers 1 and 3 expanded into user stories.

Understanding 63 of the project. For each task, information is recorded regarding the following: • when it needs to be completed; • the person assigned to do the work; • any deliverables that will result. Common steps for creating a work plan include the following: • Identify the tasks that need to be accomplished.

• Determine how long each one will take. • Organize the task in a Gantt chart. Figure 3.8 shows a portion of a Gantt chart for the initial stages of the optical care system development. Figure 3.8 lists the tasks to be com- pleted for the initiation stage of this particular project. For each task, the start and end dates are estimated.

The example also shows the percentage of completion and the initials of the team members in charge of complet- ing each task. Although the example only shows the initial stages of the project, the product owner or project manager needs to plan all the activi- ties needed to analyze, design, implement, test, and deploy the full sys- tem. That is, the product owner needs to estimate the time and effort needed to complete the project in full.

Then, the product owner or project manager will use the same Gantt chart to monitor progress and mark when tasks are completed. However, creating an accurate Gantt chart is not an easy task.

World Scientific Publishing Co. Pte. Ltd. 5 Toh Tuck Link, Singapore 596224 USA office: 27 Warren Street, Suite 401-402, Hackensack, NJ 07601 UK office: 57 Shelton Street, Covent Garden, London WC2H 9HE Library of Congress Control Number: 2025054215 British Library Cataloguing-in-Publication Data A catalogue record for this book is available from the British Library. LECTURE NOTES ON COLLABORATIVE SOFTWARE PROJECTS Practices, Concepts, And Key Events for Designing, Managing, and Prototyping Successful Products Copyright © 2026 by World Scientific Publishing Co.

Pte. Ltd. All rights reserved. This book, or parts thereof, may not be reproduced in any form or by any means, electronic or mechanical, including photocopying, recording or any information storage and retrieval system now known or to be invented, without written permission from the publisher. For photocopying of material in this volume, please pay a copying fee through the Copyright Clearance Center, Inc., 222 Rosewood Drive, Danvers, MA 01923, USA.

In this case permission to photocopy is not required from the publisher. ISBN 9789819825844 (hardcover) ISBN 9789819825851 (ebook for institutions) ISBN 9789819825868 (ebook for individuals) For any available supplementary material, please visit https://www.worldscientific.com/worldscibooks/10.1142/14662#t=suppl Desk Editors: Soundararajan Raghuraman/Veronica Lee Typeset by Stallion Press Email: [email protected] Printed in Singapore For my undergraduate students, with gratitude, for the honor of teaching you and for the countless ways you have deepened my understanding of what it means to teach.

This page intentionally left blank vii Foreword “A good teacher can inspire hope, ignite the imagination, and instill a love of learning.” — Brad Henry In the ever-evolving landscape of computing and information technology, few educators have made as profound an impact as Dr. Alejandra J. Magana. As the W.C. Furnas Professor in Enterprise Excellence at Purdue University, Dr. Magana has not only shaped the minds of thousands of students but has also redefined how systems analysis and design are taught in higher education.

This book is a testament to her visionary approach to teaching—an approach rooted in transformative pedagogy, cooperative learning, and the Scrum framework. Drawing from over 15 years of experience teach- ing large-scale undergraduate courses, Dr. Magana has crafted a learning experience that mirrors the collaborative, iterative, and problem-solving nature of real-world software development. Her integration of agile meth- odologies into the classroom has empowered students to become not just learners but also contributors and leaders in systems development teams.

What sets this work apart is its seamless blend of technical rigor and human-centered design. It guides readers through the full lifecycle of systems development—from requirements elicitation to interface design and architectural modeling—while emphasizing the interpersonal skills that make teams thrive. The inclusion of real-world case studies, viii Lecture Notes on Collaborative Software Projects team-based projects, and practical tools for collaboration reflects Dr. Magana’s belief that effective systems are built not just with code, but with communication, empathy, and shared purpose.

This is a short excerpt from the opening of “” by Unknown, quoted for review and introduction purposes. All rights belong to the copyright holders.

Book Information

• Unique ID: 7d3a301fea8727de
• File Extension: .pdf
• File Size: 11,222,444 bytes (10.703 MB)
• Title: –
• Author: Unknown
• ISBN: 9789819825844, 9789819825851, 9789819825868
• Pages: 191
• Language: English (en)

Reading & Word Statistics

• Estimated Reading Time: 236.07 minutes
• Total Words: 47,215
• Total Characters: 314,586
• Average Words per Page: 247.2
• Average Characters per Page: 1647.05

Most Frequent Words

system (551), figure (222), design (204), requirements (201), software (181), systems (179), team (174), use (170), user (170), data (162), class (158), product (157), diagram (152), example (137), development (134), also (123), scrum (118), diagrams (117), project (116), time (113), case (111), one (108), projects (106), information (105), business (100), process (98), collaborative (97), classes (96), functional (93), model (90), lecture (89), notes (89), work (89), communication (88), analysis (84), management (83), interface (81), between (81), used (78), components (78), models (76), users (74), use-case (72), needs (71), sprint (71), patient (71), server (70), different (68), understanding (67), specific (66), architecture (65), appointment (65), teams (64), schedule (64), members (64), object (63), focus (63), layer (62), order (62), need (62), functionality (60), sequence (59), able (59), skills (58), course (58), cases (58), include (58), often (57), within (55), stage (55), planning (54), objects (54), events (53), modeling (52), client (51), care (51), relationships (50), relationship (50), activity (49), application (48), network (47), cultural (47), two (47), book (46), form (46), thinking (46), backlog (46), optical (46), first (45), high (45), manage (44), view (44), new (42), like (42), access (42), approach (41), step (41), actors (41), including (40), technical (40).

PDF Download