2 系统方法&SDLC示例

最新推荐文章于 2026-06-24 14:00:17 发布

原创最新推荐文章于 2026-06-24 14:00:17 发布 · 689 阅读

15 ·

本内容遵循CC 4.0 BY-SA版权协议

GEO检测

标签

#运维 #软件工程 #项目管理

系统分析与项目管理专栏收录该内容

10 篇文章

订阅专栏

一、系统方法（Core Principle of Project Management: Systems Approach）

1. 系统方法的起源与核心（Origin and Core of the Systems Approach）

起源：20 世纪 50 年代出现，是一种用于管理和解决问题的分析性方法，强调从 “整体视角” 而非孤立视角看待项目。systems thinking

The systems approach emerged in the 1950s as an analytical method for management and problem-solving, emphasizing a holistic rather than isolated view of projects.

2. 三大组成部分（Three Components）：

组成部分（Component）	核心内容	Core Content
系统哲学（Systems Philosophy）	将项目及所处环境视为 “系统整体”，而非独立模块，需考虑各要素间关联	Views the project and its environment as an "integrated system" rather than independent modules, considering the connections between various elements4
系统分析（Systems Analysis）	以 “解决问题” 为目标的分析框架，通过拆解问题、梳理逻辑找到最优方案	An analytical framework aimed at "problem-solving", finding the optimal solution by breaking down problems and organizing logic
系统管理（Systems Management）	对系统（如组织 IT 体系）进行变更前，优先解决业务、技术、组织三大维度的潜在问题，避免孤立决策	Before making changes to a system (e.g., an organization's IT system), prioritize solving potential issues in the three dimensions of business, technology, and organization to avoid isolated decision-making6

3. 项目管理的 “三领域模型”（Three-Sphere Model for Project Management）

该模型是系统管理的具体落地工具，要求项目决策需同时覆盖 “业务、技术、组织” 三大领域.

领域（Sphere）	核心关注点（Core Focus）
业务领域（Business Issues）	成本、维护费用、注册影响
	Costs, maintenance fees, enrollment impact
技术领域（Technological Issues）	硬件规格、所需应用、网络影响
	Hardware specifications, required applications, network impact
组织领域（Organizational Issues）	覆盖范围、开发责任人、培训责任人
	coverage, developers, training providers

4. 项目生命周期（Project Life Cycle）

4.1 生命周期的定义与核心要素（Definition and Core Elements of the Life Cycle）

定义：项目生命周期是项目阶段的集合，明确每个阶段需执行的工作、将产生的可交付成果、参与人员，以及管理层如何控制和批准各阶段产出。

Definition: A project life cycle is a collection of project phases that defines the work to be performed in each phase, the deliverables to be produced, the participants involved, and how management will control and approve the work produced in each phase.

可交付成果：作为项目一部分生产或提供的产品或服务，如技术报告、培训课程、硬件设备等

Deliverables: Products or services produced or provided as part of a project, such as technical reports, training sessions, and hardware1

4.2 各阶段关键特征（Key Characteristics of Each Phase）

生命周期分为 “早期、中期、末期”，各阶段在资源需求、不确定性、利益相关者影响力上差异显著

divides the life cycle into "early phase, middle phase, and final phase", with significant differences in resource requirements, uncertainty, and stakeholder influence across phases:

阶段（Phase）	资源需求（Resource Requirement）	不确定性（Uncertainty）	利益相关者影响力（Stakeholder Influence）	核心目标（Core Goal）
早期阶段（Early Phase）	最低（Lowest）	最高（项目方向、需求未完全确定）	最高（可通过反馈调整核心决策）	明确项目目标、可行性分析、获启动批准
		（Highest - project direction and requirements not fully determined）	（Highest - core decisions can be adjusted via feedback）	Clarify project goals, conduct feasibility analysis, and obtain approval for initiation
中期阶段（Middle Phase）	最高（需投入大量人力、技术资源）	降低（需求、方案明确，风险可控）	降低（项目方向固定，调整空间有限）	执行开发与测试，推进可交付成果落地
	（Highest - substantial human and technical resources needed）	（Reduced - requirements and plans clear, risks controllable）	（Reduced - project direction fixed, limited room for adjustment）	Execute development and testing, and promote the implementation of deliverables
末期阶段（Final Phase）	降低（资源逐步撤离）	最低（成果近收尾，风险已解决）	最低（仅反馈细节问题，难改整体方向）	完成系统测试、用户验收，确认需求是否满足、获赞助商收尾批准
	（Reduced - resources gradually withdrawn）	（Lowest - deliverables nearly finalized, risks resolved）	（Lowest - only minor issues can be feedback, little ability to change overall direction）	Complete system testing and user acceptance, confirm if requirements are met, and obtain sponsor approval for closure

5. 影响 IT 项目管理的最新趋势（Recent Trends Affecting IT Project Management）

5.1 全球化（Globalization）

定义（牛津词典）：因大型跨国公司影响及通信技术改善，全球不同文化和经济体系正变得相互关联且相似。

Definition (Oxford Dictionary): Different cultures and economic systems around the world are becoming connected and similar due to the influence of large multinational companies and improved communication.

核心挑战：沟通（communication）、信任（trust）问题。

Core Challenges: Communication and trust issues.

5.2 外包（Outsourcing）

定义：组织从外部来源获取货物和 / 或资源；若外包对象来自其他国家，称为 “离岸外包（Offshoring）”。

Definition: An organization acquires goods and/or resources from an outside source; if the outsourcing is from another country, it is called "offshoring".

5.3 虚拟团队（Virtual Teams）

定义：一组跨越时间和空间，利用通信技术开展工作的个人。

Definition: A group of individuals who work across time and space using communication technologies.

核心问题：虚拟团队面临哪些挑战？如何给出建议？

Core Questions: What are the issues of virtual teams? What are your suggestions for virtual teams?.

Virtual teams face several key issues:

Communication challenges: Due to differences in time zones, team members may find it hard to have real - time communication. Also, relying on digital communication tools can lead to misunderstandings as non - verbal cues like body language and tone of voice are missing.
Trust issues: Without face - to - face interactions, it's difficult for team members to build and maintain trust. They might feel less connected to each other and the project.
Collaboration inefficiencies: Working across different time zones and locations makes it tough to schedule meetings and coordinate work. Sharing and updating documents in real - time can also be problematic.
Cultural differences: If team members come from different cultural backgrounds, there can be differences in work styles, communication norms, and decision - making processes, which may cause conflicts.

To address the challenges faced by virtual teams, here are some suggestions:

Establish clear communication norms: Set regular meeting times that accommodate different time zones. Use video conferencing tools as much as possible to allow for non - verbal communication. Create guidelines for response times to messages.
Build trust through team - building activities: Organize virtual team - building events, such as online games or virtual coffee breaks, to help team members get to know each other on a personal level. Share team member profiles (including interests and backgrounds) to foster a sense of connection
Use collaborative tools effectively: Adopt project management software for task tracking and document sharing. Ensure all team members are trained on using these tools to facilitate real - time collaboration and version control of documents.
Respect and leverage cultural differences: Encourage team members to share their cultural perspectives and work styles. Train the team on cultural competence to help members understand and appreciate diversity, which can lead to more innovative problem - solving.

SDLC示例

“6 天完成一次迭代” 为例，完整演示 SDLC 六大核心流程的落地，各流程对应每日关键活动：

SDLC 核心流程	对应天数	关键活动
1. 识别问题与获批准	前期	- 制定《系统愿景文档》，明确问题描述（需开发便携系统提升代理与总部沟通效率）、系统能力、商业价值 - 与管理层等利益相关者沟通，获项目启动批准及预算
2. 项目计划与监督	第 1 天	- 拆分核心功能模块：优先开发供应商信息子系统 - 制定工作分解结构（WBS），明确任务（如需求调研、设计、开发、测试）、资源分配（人员分工）、时间排期- 用 Microsoft Project 等工具辅助任务管理
3. 需求发现与细节理解	第 2-3 天	- 第 2 天（初步调研）：访谈采购经理 / 代理、观察工作流程，输出用例列表（如 “查找供应商”“录入 / 更新联系人信息”）、域类列表（如 Supplier、Contact）及初步类图 - 第 3 天（深入分析）：梳理用例详细工作流（如 “查找供应商” 需支持输入名称、返回信息、关联查看联系人），绘制用例图、活动图，设计初步界面草图（如供应商搜索页）
4. 系统组件设计	第 4 天	- 数据库设计：为供应商子系统设计两张关联表（Supplier 表：含 SupplierID（主键）、名称、地址等；Contact 表：含 ContactID（主键）、SupplierID（外键）、联系方式等） - 架构设计：确定系统运行载体（浏览器 / Windows / 智能手机），绘制架构配置图（如浏览器 - 互联网 - 服务器 - 子系统的交互关系） - 类图设计：区分视图层（如 SupplierView、ContactView，负责查询 / 展示）与域层（如 Supplier、Contact，负责数据处理）
5. 组件开发、测试与集成	第 5 天	- 按用例分模块编程（示例：用 PHP 开发 SupplierView 类，实现 “查找供应商”“展示供应商信息” 功能） - 执行单元测试（测试单个功能，如数据查询）与集成测试（验证模块间交互）
6. 系统测试与部署	第 6 天	- 功能测试：验证系统是否满足所有需求（如信息录入、查询功能）- 用户验收测试：由采购代理等用户验证系统可用性- 按需部署部分系统功能