Home|News blank.gif
When Design Matters CoreLinux++ CoreLinux Consortium
blank.gif
CoreLinux++
blank.gif
Goals
blank.gif
Developer's Corner
blank.gif
Contacts
Memory Use Case Report
Memory Use Case Report
Generated at: Tue, Apr 11, 2000
08:09:19



TABLE OF CONTENTS
REPORT BODY

Use case report


Class report
Data package
Component View package
Use Cases package
Participants package
Developer class
Implementor class
Analysis package
[Unnamed] class
Processes class
PersistentStorage class
TransientStorage class
OperatingSystem class
Storage class
[Unnamed] class
Memory class
libcorelinux package

Model dictionary

SUMMARY


REPORT BODY

Use case report
use case Allocate memory
Documentation:
This use case describes the desire on the callers part to allocate some amount of storage from the memory subsystem.
Extends:
  Get memory use case



use case Use memory
Documentation:
This use case describes the desire on the caller to get access to a storage area in memory that is presumed present.
Extends:
  Get memory use case



use case Read memory
Documentation:
Use case for reading areas of the memory storage.


use case Write memory
Documentation:
Use case for writing to areas of the memory storage.


use case Release memory
Documentation:
Use case describing the releasing or returning of a storage area backed by the memory subsystem.


use case Get memory

actor Developer
Documentation:
Developer


actor Implementor
Superclasses:
Data::Use Cases::Participants::Developer

Documentation:
Implementor is a developer that uses either the corelinux or extension types into solution space applications.




Class report

package Data

package Data::Component View

package Data::Use Cases

package Data::Use Cases::Participants
class Developer
Stereotype:   <<actor>>
Documentation:
Developer

class Implementor
Superclasses:
Data::Use Cases::Participants::Developer

Stereotype:   <<actor>>
Documentation:
Implementor is a developer that uses either the corelinux or extension types into solution space applications.
Operations:
public   doWork ( )


package Data::Analysis
class [Unnamed]

class Processes
Stereotype:   <<thread>>
Documentation:
An execution path that the operating system schedules for activity. Each process calls upon the operating system to allocate, use, and remove various storage resources.

class PersistentStorage
Documentation:
Characterized as long term storage. Content is maintained across system initialization.

class TransientStorage
Documentation:
Characterized as short term storage. Does not maintain content across system initializations.

class OperatingSystem
Documentation:
The operating system manages storage resource for both itself and user processes.

class Storage
Documentation:
Storage available, and to some extent managed, from the system.

class [Unnamed]

class Memory
Superclasses:
Data::Analysis::TransientStorage

Documentation:
Memory is a high speed transient storage object.


package Data::libcorelinux


Model dictionary
A   C   D   G   I   L   M   O   P   R   S   T   U   W   

A

Allocate memory use case from package Use Cases
This use case describes the desire on the callers part to allocate some amount of storage from the memory subsystem.
Analysis package

C

Component View package

D

Data package
Developer actor from package Use Cases.Participants
Developer
Developer class from package Use Cases.Participants
Developer
doWork operation from class Use Cases.Participants.Implementor

G

Get memory use case from package Use Cases

I

Implementor actor from package Use Cases.Participants
Implementor is a developer that uses either the corelinux or extension types into solution space applications.
Implementor class from package Use Cases.Participants
Implementor is a developer that uses either the corelinux or extension types into solution space applications.

L

libcorelinux package

M

Memory class from package Analysis
Memory is a high speed transient storage object.

O

OperatingSystem class from package Analysis
The operating system manages storage resource for both itself and user processes.

P

Participants package from package Use Cases
PersistentStorage class from package Analysis
Characterized as long term storage. Content is maintained across system initialization.
Processes class from package Analysis
An execution path that the operating system schedules for activity. Each process calls upon the operating system to allocate, use, and remove various storage resources.

R

Read memory use case from package Use Cases
Use case for reading areas of the memory storage.
Release memory use case from package Use Cases
Use case describing the releasing or returning of a storage area backed by the memory subsystem.

S

Storage class from package Analysis
Storage available, and to some extent managed, from the system.

T

TransientStorage class from package Analysis
Characterized as short term storage. Does not maintain content across system initializations.

U

Use Cases package
Use memory use case from package Use Cases
This use case describes the desire on the caller to get access to a storage area in memory that is presumed present.

W

Write memory use case from package Use Cases
Use case for writing to areas of the memory storage.

SUMMARY
Total packages reported:     6
Total classes reported:      10
Total operations reported:      1
Total use cases reported:    6


Copyright © 1999, 2000 by CoreLinux Consortium
This material may be distributed only subject to the terms and conditions set forth in the Open Publication License
Contacts
- contact the webmaster
News
Powered / Hosted by

SourceForge.net
Contributor
NoMagic, inc.
thanks Gary!
Cool OO Sites
cetus
corba
omg
patterns
  Made with xemacs / php Comments to webmaster blank.gif