You are hereBlogs

Blogs


Photo!

Shounan Mini Cal Poly : 20080829: :)Shounan Mini Cal Poly : 20080829: :)
:9

湘南Cal Poly 2008/08/27

UML Domain
Dr.Guthrie

System Design

USE Cases システムの概要を記録
追加のための部品としてバーーコードなどがある。

次のステップ
 プロトタイプインタフェース(Prototype Interface)の準備

Feature
 Planner
★Program Manager  仕様作成
Tester
 Programmer

ツールの紹介
  Visioを使用して
・画面デザイン
・ロバストネス

ROBUSTNESS ANALYSIS
1.Boundary Objects
2.Control Objects
3.Entity Objects

Interaction Diagrams
・Sequence Diagram

Class Structure
Three sections
Class name

メンテナンスしやすい

ラウンドトリップエンジニアリング Round trip Engineering

演習  C#で 炊飯器 パネル コーディング

CRC Card

演習  図書館 4つのシナリオに基づき、CRC Cardを作成

Summary on 27 Aug 2008 by Sugano

System Design by Dr.Guthrie

-Prototype Interface
-Robustness Analysis
-designing by VISIO
-Interaction Diagram
-Messages
-Class Diagram
-

080827_1241~001.jpg

8/27 湘南Cal Poly Report(K.Mori)

【Dr.Guthrieの講義】
Prototype Interfaces
・ユーザーインターフェース(画面)

Robustness Diagram
・Boundary Objects:境界オブジェクト(GUIの部品等、Control Objectsと対話出来るが、Entity Objectsとは対話出来ない)
・Control Objects:コントロールオブジェクト(メソッド、機能)
・Entity Objects:実体オブジェクト(Control Objectsに相互作用する)

Sequence Diagram
・処理の流れを書く(操作によって発生する処理など)
・処理を実線、戻り値を点線で表す
・Visioにて実習

Class Diagram
・ソフトウェアとインタフェースのための仕様
・ソフトウェアの最終的な(静的な)設計
表記
 +:public
 -:private
 #:protected

CRC Card(Class Responsibility Collaborator)
・1つのクラスを責務と関係(協調性)に分けて記入
・親クラス、子クラスなども記入
・グループでの演習(図書館での4つのシナリオを考える)

Homework is finished!!

A little time ago, my homework is finished!!
I'm happy.
Because I'm sleepy.

Today,I learned UML,CRC card,and more.
It is fun to learn that.

I will try to speak English tomorrow.
Good-night!!

2008/08/27 Ellie Kim

[ Dr. Guthrie ]

Prototype Interface

Rice Cooker
- Button, LCD, Label

Library
- Input keyword
- Click "search" button
- System searches catalog
- System displays search result

=> Feature

- Planner
- Program Manager
- Testser
- Programmer

System Design

with MS Visio 2007

Robustness Analysis

good for complicated systems, like maps...
Not a formal part of the UML (it's additional software developer)

Boundary Objects
- GUI Components, as we saw at Visio
- for Actor Users

Control Objects
- methods, functions, behavior, operations depends on each program...
- can interract with other Control Object, cant with users.

Entity Objects
- software classes that we will design
- real world concepts
- store data, only interact Control Objects

Interaction Diagrams

Illustrates how instances of software classes interact via "messages"
- to understand messages between different methods

Sequence Diagram
- order of the operations, not static.
- time : top to bottom
- designing the real s/w
- using the real name of the classes or the methods

Three kinds of messages
- action : (click)
- function : functionA(parameter) : solid line,
- return value : dotted line, not necessery)

Associations

think about the reason the variables are private and the methods are public

Attribute/Method Visibility

+ public access
- private access
# protectes access

Rice Cooker

- homework

CRC card

Class, Responsibility, Collaboration
for brainstorming, for designing OOS,

- class name
- super/sub-classes
- responsibilities, collaborations
- attributes on the back

Assignment

Write list(name) of four library system scenarios
Then work through each scenario with team and make/fill out CRC
- all by hand

[ Free Discussion ]

confidentiality, integrity, availability
+ Integrity and Authenticity, Confidentiality and Possession, Availability and Utility

Enjoy your work !

The goal of a team project is similar as personal project.
PSP (what to do) -> TSP (what the project is)

Web Security
- port : 80 http 443 https
- Cqual injection
- Threat modeling

2008/08/27

(1)OOM(Dr.Guthrie)
Use case
*Prototype Interface(Visio)
 ユーザインタフェース
*Robustness Diagram(Visio)
 データの流れ
*Sequence Diagram(Visio)
 処理の流れ
*Class Diagram(Vision)
 静的な関係
*Round Trip Engineering(Visual Studio)
 コードとDiagramの関連リンク
*CRC card(Paper)
 Class Responsibiry Card
 クラスの責任と関連

(2)Free
*各国のビジネス習慣の違い
*日本とアメリカのIT Costの違い

2008/08/26 Ellie Kim

[ Dr. Guthrie ]

What is Object?
- It's "REAL" by Ms. Shou
- 3 parts : identity, state, behavior

Why Object?
- reusable
- easy to understand

1. Modularity: The source code for an object can be written and maintained independently of the source code for other objects. Once created, an object can be easily passed around inside the system.
2. Information-hiding: By interacting only with an object's methods, the details of its internal implementation remain hidden from the outside world.
3. Code re-use: If an object already exists (perhaps written by another software developer), you can use that object in your program. This allows specialists to implement/test/debug complex, task-specific objects, which you can then trust to run in your own code.
4. Pluggability and debugging ease: If a particular object turns out to be problematic, you can simply remove it from your application and plug in a different object as its replacement. This is analogous to fixing mechanical problems in the real world. If a bolt breaks, you replace it, not the entire machine.
(http://java.sun.com/docs/books/tutorial/java/concepts/object.html)

Use Case
What's the process of the Rice Cooker and the Human-being?
- can be the system side and the acter side.
- think more about the expensions.

[ Dr. Manson ]

Why do we need PSP?

What is the difference between PSP and TSP?
PSP : Personal Software Process
TSP : Team Software Process

Homework
Time Recording Log, Defect Recording, A Game

[ Dr. Isshiki ]

Project Management Office (PMO)
Business Requirements
User Requirements
- functionality, usability, performance, security, legal compliance

Gas Station
- report the business requirements

[ Dr. Guthrie ]

What was the Expensions?

1. IF didn’t plugged
- push the COOK button - nothing heppens - cannot get the cooked rice

To prevent the problem
- add Special Clock with separate power will check the alarm and the plug.
- it will warn if it's unplugged
- if unplugged while cooking, it will give loud warning sound

2. IF no water
- only rice is cooking
- rice will be burned out, so the actor can get only charcoals

To prevent the problem
- add a Sensor, checking the existance of the water and the rice
- it will check and warning

Use Case of a Library
create user (patron)
Check out
Check in (return) book
Add new book to inventory
Catalog Search
Reserve (put on hold) book

Ranking Matrix
check Risk, Coverage, Criticality

Ranking Matrix of Rice Cooker
1. cook the rice
2. cook gruels
3. steam - meat, vegitables
4. cook drinks
5. warm the results
6. warn problems

What can be the object of the Rice Cooker?
rice cooker, software, plate, bowl, human, buzzer, light, sensor, plug, enemy ...

[ Dr. Isshiki ]

Cloud Computing
If Windows disappears? - Mac?
Why Google Documents?
"No change, No Future.t"
Convergence, Mash-ups

registered this blog
elliekim

8/26 湘南Cal Poly Report(K.Mori)

【Dr.Guthrieの講義】
Ocject Oriented Methodology
What Object? = "Real"
なぜObectを使うか
1.再利用性が良い
2.理解しやすい

複数個のケースを作成するが、問題はどのケースを初めに行えばよいか?
・一番重要なケースを作る
 →重要な欠点などを見つけることが出来るから

ゲームを例としたObjectの説明

★演習
 ・Use Caseの作成(炊飯器)
 ・失敗のシナリオを作成
 ・Ranking Matrixの作成

【Dr.Mansonの講義】
PSP/TSP
・PSP:個人の開発スキル
・TSP:プロジェクトとしての開発スキル

Phrogramのインストール

★課題(8/28 16:20まで)
 ・Phrogramを使ってプログラムを作る
 ・Defect Recording Log
 ・Time Recording Log

【Dr.Isshikiの講義】
要求を取りまとめるプロセス
・要求取得
・要求仕様
・要求検証
・要求管理

要求とは、経営者、ユーザー、開発で三者三様である。
要求定義上使ってはイケない言葉(曖昧な言葉)
・綺麗、使いやすい、見た目がイイ などの各々によって捉え方が異なるもの

機能要求
 業務要求:経営者(経営要求(※重要:ビジョン/スコープ記述))
 ユーザー要求:ユーザー(ユースケース)
 システム要求:ユーザー(ソフトウェア要求仕様書)
 ソフトウェア要求:開発者(ソフトウェア要求仕様書)

非機能要求
 業務ルール、法律
 品質・属性、待ち時間
 外部I/F
 制約

SaaS and SOA
・変わらない人、会社、組織は潰れる。
・ITの今後

★演習
 ガスステーションシステム



Search

Who's online

There are currently 0 users and 1 guest online.