[L11][16/11/2025][S1 2025-26] SE440 Software Project Management

Software Engineering and Project Management Overview

Introduction to Software Engineering

• The discussion begins with an overview of software engineering and project management, emphasizing the foundational questions that may arise in this field.

• A reminder is given to students from non-software engineering backgrounds, highlighting that many concepts will be straightforward for those familiar with the discipline.

International Standards in Software Engineering

• The speaker introduces international standards relevant to software engineering, specifically mentioning the evolution of the Software Engineering Body of Knowledge (SWEBOK).

• SWEBOK Version 3 was released in 2004 with 15 knowledge areas; it later evolved into Version 4, which includes 18 knowledge areas.

Importance of Standards

• The significance of adhering to standards such as ISO/IEC 19759 is discussed, noting its initial release in 2005 and subsequent updates.

• The latest version from 2024 emphasizes the necessity for standards in project management and development processes.

Role of Standards in Project Management

• One key success factor highlighted is maintaining standards during project development to ensure quality and consistency.

• In Jordan, compliance with specifications from regulatory bodies is essential when producing any product or establishing a factory.

Application of Standards

• Standards serve as a reference point for product specifications and project management practices. Adhering to these can lead to better organization within projects.

• The speaker stresses that understanding these standards is crucial not only for software engineers but also for anyone involved in project management across various fields.

Knowledge Areas According to SWEBOK Version 3

Overview of Knowledge Areas

• There are initially identified knowledge areas including software requirements, design, construction, deployment, and maintenance.

Focus on Maintenance

• Maintenance has been underemphasized despite being highlighted since SWEBOK's first version; there remains a lack of comprehensive resources on this topic.

Future Work on Maintenance

• The speaker mentions plans to develop a complete book focused on software maintenance life cycles due to its importance in industry practices.

Software Engineering and Configuration Management

Overview of Software Engineering Concepts

• The discussion begins with a focus on software engineering, particularly in relation to configuration management, which has been recognized as a knowledge area since 2004.

• Emphasis is placed on version control systems, highlighting the importance of managing old and new versions of software before implementing upgrades or replacements.

Importance of Rollback Procedures

• The necessity for rollback procedures is discussed; if issues arise after an upgrade, reverting to the previous version can help bypass problems while they are addressed.

• Rollbacks allow teams to return to a stable point in development, ensuring continuity and minimizing disruption during troubleshooting.

Layers of Configuration Management

• Configuration management applies across all layers of infrastructure, including hardware and software systems. Each layer requires specific configurations for optimal performance.

• Examples include cloud-based hardware setups and local computer centers that necessitate internet connectivity configurations for security and privacy.

Hardware and Software Interactions

• The relationship between hardware components (like motherboards and memory) and their configurations is crucial for system functionality.

• Operating systems also require specific configurations to function effectively atop the hardware layer, influencing how applications run.

Application-Level Configurations

• Applications such as Microsoft Office have their own configuration settings that users must manage for optimal use. This includes adjustments like font size or document formatting.

• Network configurations are essential beneath the hardware level, indicating that configuration management encompasses both physical devices and network settings.

Process Models in Software Engineering

Focus on Processes

• The course emphasizes various processes within software project management, referencing chapters from relevant literature that discuss methodologies extensively.

Models and Methods Utilization

• Different models and methods are integral to any engineering field. Understanding these frameworks helps streamline project execution regardless of discipline (software engineering included).

Simulation in Training

Flight Simulation Example

• A flight simulator example illustrates how training through simulation prepares individuals for real-world scenarios without risk. It highlights the importance of theoretical knowledge combined with practical experience.

Benefits of Simulation

• Simulators provide a safe environment where trainees can learn about aviation dynamics before actual flights. This method reduces potential errors when transitioning to real aircraft operations.

Modeling Systems

Evaluation Through Modeling

• Modeling allows engineers to evaluate system designs before implementation. While it may not capture every detail perfectly, it significantly reduces risks associated with direct construction efforts.

Discovery of Errors

• Early modeling helps identify approximately 60% of potential errors prior to building the actual system. This proactive approach aids in refining designs before full-scale implementation occurs.

Software Engineering Insights

Challenges in Software Development

• The speaker discusses significant losses due to issues in the software series, emphasizing the need to redo work which results in wasted efforts and additional costs for employees.

• Despite potential problems during implementation, the speaker believes that these will be minimal if a proper model is created using simulation tools, leading to manageable issues post-development.

Role of Modeling in Software Engineering

• Modeling overlaps with analysis and design phases but must occur before construction; it ensures that the system's design is sound before moving forward.

• The importance of quality assurance is highlighted, noting that project managers should integrate quality practices into their workflow alongside engineering principles.

Professional Practices in Software Engineering

• The discussion introduces professional practices within software engineering as essential components recognized by organizations like IEEE.

• Certification processes such as obtaining a Professional Engineer (PE) license are explained, requiring mastery over various aspects of software engineering including ethics and regulations.

Ethical Standards and Regulations

• Emphasis on ethical practice within engineering professions includes adherence to laws and transparency, which are crucial for maintaining integrity.

• Engineers must understand local regulations related to their field when pursuing certifications like PE in software engineering.

Foundations of Software Engineering Education

• Historical context is provided regarding the inclusion of economics as a core subject for engineers, highlighting its relevance even decades ago.

• The evolution of course titles reflects changes in focus areas; "Software Engineering Economics" emphasizes project management aspects specific to software projects.

Core Knowledge Areas in Software Engineering

• Fundamental computing concepts form the backbone of software engineering education, covering programming languages, data structures, networking, and concurrency.

• Discrete mathematics becomes essential for understanding algorithms and data structures rather than traditional calculus topics.

Updates on Knowledge Areas

• Recent updates include new knowledge areas such as software architecture and cybersecurity being recognized separately from general design principles.

• A shift towards operational knowledge areas indicates an evolving landscape where practical application becomes increasingly important.

This structured summary captures key insights from the transcript while providing timestamps for easy reference.

Functional vs Non-Functional Requirements

Understanding Functional Requirements

• Functional requirements define the services and operations that a system must perform, including expected outputs and data manipulations.

• They focus on the inputs and outputs of processes, emphasizing correctness and precision in delivering results.

Exploring Non-Functional Requirements

• Non-functional requirements pertain to performance metrics, which can vary based on user perspectives; what is acceptable for one user may not be for another.

• An example involves ATM machines where younger users may find a 90-second wait unacceptable, while older users might consider it reasonable.

User Perspective in Performance Evaluation

• The performance of systems like ATMs can be judged differently by various demographics, highlighting the subjective nature of non-functional requirements.

• This variability emphasizes that performance quality factors are crucial in assessing user satisfaction across different age groups.

Quality Factors and Measurement

• Performance is categorized as a quality factor measured through specific metrics; other factors include privacy and security.

• A well-defined quality metric helps determine whether a product meets acceptance criteria based on its performance attributes.

Product vs Process Requirements

• Distinctions exist between product-specific requirements (e.g., packaging, download options for software) versus functional/non-functional requirements related to the product's operation.

• System infrastructure and tools used for development also constitute essential requirements that influence project execution.