Dong Ming
Community@jdm4pku · Tokyo
My name is Dong Ming , I am a student from Peking University. Enrolled in 2019, and plans to graduate in 2028.
Agent Skills by Dong Ming
Showing 44 vetted skills indexed across 1 GitHub repositories.
jdm4pkuchange-control-process
Establish and operate a change control process for baselined requirements.
jdm4pkuprioritization-advisor-re
Recommends requirements prioritization methods based on stakeholder count, requirement volume, and decision context.
jdm4pkurequirements-status-tracking
Track requirements through lifecycle states and generate status distribution dashboards with progress metrics.
jdm4pkurequirements-management-process
Establish requirements baselines, version control, attribute tracking, and status monitoring for projects.
jdm4pkurequirements-traceability
Build and maintain a requirements traceability matrix linking objectives, requirements, design, and tests.
jdm4pkurequirements-validation-process
Validate software requirements through inspections, prototyping, and conceptual testing before baselining.
jdm4pkurequirements-testing
Derive test cases from requirements, use cases, and business rules before development.
jdm4pkurequirements-elicitation-workshop
Plan and execute structured requirements elicitation sessions using interviews, workshops, and observation.
jdm4pkubusiness-rule
Document business rules as structured, traceable specifications separate from functional requirements.
jdm4pkuchange-impact-analysis
Assess implications, affected work products, and effort for proposed requirements changes.
jdm4pkuuse-case
Write structured use case specifications with triggers, flows, and exceptions.
jdm4pkuobservation-analysis
Plan and conduct observation sessions to discover unstated requirements from real user workflows.
jdm4pkusrs-document
Create a Software Requirements Specification with labeled requirements, data dictionary, and interface sections.
jdm4pkuprototyping-strategy
Select prototyping approaches based on project risks, fidelity needs, and evaluation goals.
jdm4pkuvision-and-scope
Create a vision and scope document defining business objectives, project boundaries, and stakeholder context.
jdm4pkuanalysis-advisor
Recommends requirements analysis and modeling techniques based on system characteristics and team experience.
jdm4pkuquestionnaire-design
Design requirements questionnaires with structured question types, scales, and bias-resistant ordering.
jdm4pkuvalue-cost-risk-analysis
Prioritize requirements using a weighted value, cost, and risk scoring model.
jdm4pkuwriting-requirements
Write clear, testable software requirements using EARS templates and quality checklists.
jdm4pkurequirements-risk-assessment
Identify and prioritize requirements engineering risks using condition-consequence statements and exposure scoring.
jdm4pkudata-dictionary
Define data elements, structures, and compositions using formal data dictionary notation.
jdm4pkurequirements-development-process
Orchestrates the end-to-end requirements development lifecycle from vision through validated baseline.
jdm4pkucontext-diagram
Create system context diagrams defining boundaries, external entities, and data flows.
jdm4pkurequirements-baselining
Establish versioned requirements baselines with entry criteria, approvals, and configuration management.
Frequently Asked Questions About Dong Ming
FAQPage SchemaWhat tasks can I accomplish using Dong Ming's requirements engineering skills?▼
You can elicit requirements via interviews, workshops, observation, and questionnaires; write SRS documents, use cases, user stories, and acceptance criteria; model data, states, processes, and decision tables; prioritize with MoSCoW or value/cost/risk scoring; and manage baselines, traceability, and change control.
Who are these requirements engineering skills designed for?▼
They target requirements engineers, business analysts, product owners, and project managers working on software projects—especially regulated, safety-critical, or large-scale systems needing formal baselines, traceability, and structured validation before development begins.
How do I apply these skills in a real project workflow?▼
Start with vision-and-scope and stakeholder-analysis, then run elicitation sessions, transform outputs through analysis and modeling, specify requirements in an SRS, validate via reviews and inspections, and baseline them. Ongoing management uses status tracking, traceability, and change control per change request.
What prerequisites or dependencies do these skills require?▼
No software dependencies are required. Skills assume familiarity with software projects and access to stakeholders. Time estimates range from 5-15 minutes per requirement to 4-8 hours for full SRS validation, with end-to-end processes spanning 2-16 weeks depending on project size.
Do these skills support agile development environments?▼
Yes. The agile-requirements-process skill adapts elicitation, analysis, specification, and validation for agile delivery using just-in-time elaboration, backlog seeding, and sprint reviews. User stories follow INVEST criteria with structured, testable acceptance criteria suitable for regulated agile contexts.