大家好，我是新来的。有一点关于这方面问题请教

tanyfei

我一个外国朋友给了我一个介绍的文章，我大概看下来可能是某种管理上的软件设计，但是有很多专业词User-Stories ，Use-Case不懂。所以想请教各位。这到底是什么东西？在我国是否会有市场。谢谢

Introduction to the course (who am I, basic outline and syllabus)

Missions and Mission Statements:  What values drive your business?  What
unique problem do you want to solve?

Introduction to User-Stories
User story workshop: (students can, either solo or in groups (depends on
number of students) envision their services at high-level. A product service
implements a principle-based value solves a unique problem.

A user-story is a paragraph or two describing the basic user scenario and
purpose of the product or service.  Afterwards, students or groups present
their scenarios and some brainstorming is done.  Example services can be
presented, but it is preferred that students come up with their own.

Use-Case Introduction
Sky- and Cloud- Level Use Case Workshop: (individuals or groups develop 1-3
scenarios describing how stakeholder/actors interact with their product or
service to realize their goals).  Note that the information system or
technological implementation (IS/TI) is only *part* of the technological
service organization, so we first work at a high-level to describe the
interaction between actors (end-users) and the organization (as a "black
box") itself.  

The basic, high-level role of the IS/TI can be seen, subsequently, when the
organization is viewed as a "white box".  
Students or groups present their "black box" and "white box" organization
summaries.

System Use-Case Introduction
System Use-Case Workshop: (Individuals or Groups develop 1-5 use-cases,
first to describe their IS/TI itself as a "black box" (interaction between
actors and systems to realize goal), then subsequently as a "white box"
(system components, and external related systems as smaller "actors").  Note
that since any given organization may have many IS/TIs, the scope must be
limited to a few here.  Student however, has the tools to continue to go on
designing their IS/TI

System Design
A brief description is given on the process of breaking down system
use-cases into collaboration diagrams and class diagrams.  Students will
have the opportunity to hand draw and their collaboration- and class-
diagrams for different parts of the IS/TI system as time permits.  (A few
licenses of tool like EntERPrise Architect can be acquired for additional
fee, but this is not necessary).  Tools for system design can be discussed.

Requirements Engineering
Any given IS/TI has more requirements than just interaction between the
parts.  In addition to Functionality, we must also address Usability,
Reliability, Performance, Scalability, Suitability, and Security
requirements.

System Test
A description of different test levels (Acceptance, System,
Application-Integration, Application, Unit-Integration, and Unit, as well as
document inspection) is gone into briefly.  Also where in the realization
process these test levels are specified and executed.

Any given IS/TI can undergo testing for the attributes mentioned in
"Requirements Engineering" above and these test levels are also described.


System realization
A description of the myriad problem of finding the right resources to
implement the IS/TI is presented.  For most IS/TIs, any given
programmer/project manager may have some, but, likely not all the skills.
Fortunately, with the internet and free/cheap telephony like Skype, it is
possible to find the right people for the right price, given that the
student is not limited to where the work is done, is willing to travel and
network, and is open to different cultural ways of working.  A bit is
discussed about networking and partnerships.  

What else does my business need?
A tech service or product business is not only an organization with one or
many IS/TI's and some people trained how to use it (Never lose sight of your
original vision as described in your "User Stories" and Mission Statements,
though!)  So far, we've only addressed The "Product/Service" and the
"System" part.  You also need:
1. Legal
2. Communication
3. Cashflow

...organized around a Team, Leadership and Mission.

These things may be realized in many ways in any given society, but the
principles are the same.  Anyone interested in starting a business needs to
find the talent/partners in these areas.

A Few notes on effectiveness:
Do not dictate, but lead. Know your values and live by them. Let your team
members find their voice and self-actualize in their roles by following your
example.  Students are encouraged to talk about their good/bad experiences
in work, study, and personal relationships, and from this, what and how they
have learned.

tanyfei

请大家帮一下忙，谢谢

eversly714

个人认为这样的东西自己大概可以完成，用翻译软件翻译关键的单词应该不难，前提是你英语海可以，可以看懂很多。

柳生静云

你看看每段的Title，简单呀，这篇文章，非常简单。

系统设计、工程需求、系统测试、系统分析什么的。主要就是介绍一个系统和SKYPE这个软件的衔接什么的吧。