Thursday, March 22, 2007

Stress Test Developer position to work on industry-leading solutions, which have been proven via many angles with major industry reviews and awards, and on a team which produces and expects stellar work from every member. The most successful candidates will be motivated self-starters who can *own* their piece of the project while producing high quality code within agreed time frames and in turn ensures the continued production of our high quality suite of products. We are a very large open source shop and employ a number of other leading technologies, including virtual machines, blade and multi-core servers, etc.

Thursday, March 08, 2007

Kirk's requirement sets are included in summary below

Participate in the requirements analysis and design for software

applications or sub-components. Creates documented application

architectures, detail designs, class diagrams, use cases and coding

specifications. Participates in testing as identified in the development

methodology. Creates appropriate documentation for developed software.

Participates in the effort of developing software project plans with

well-defined tasks, deliverables, time estimates and required resources.

Collects and documents software requirements as needed to support new

development. Performs software troubleshooting and provides problem

resolution. Recommends, establishes, maintains and enforces software

development methodologies, standards and procedures. Participates and may

facilitate code walk-through to ensure code standards are applied and

maintained. Is available on call as required to support business

requirements. Documents status reports and records time expended.

Performs other duties as required.


Labels:

Saturday, March 03, 2007

VB and C# Managed Applications

1) Fields Methods Properties and Events
2) Inheritance, Base class Overriding
3)

Friday, March 02, 2007

OOP vs OOA Generic Descriptions

OOP (vs.) OOA

Requirement 1

2

3

4

5

OOP {111};1

OOA {1,1}

OOA {2,2}

OOA (1,3)

OOA (1,4)

OOA (1,5)

OOP (121);2

OOA (2,1)




OOA(2,5)

OOP (131);3


OOA {3,2}


OOA (3,4)


OOP (141);4


OOA(4,2)




OOP (151);5

OOA (1,2)


OOA (1,2)



OOP (161);6


OOA (1,2)




OOP (91);7



OOA (1,2)



OOP (181);8


OOA (1,2)



OOA (1,2)

OOP (201);9

OOA (1,2)

OOA (1,2)

OOA (1,2)

OOA (1,2)

OOA (1,2)




9x6


First build and Make file describe, lets say the following Requirement column definitions;

Requirement 1: The OOP and OOA pieces that build a VB .NET Form accessible by http://161.119.109.111/1080/

Requirement 2: The OOP and OOA pieces that build a database connection and database adapter within VB .NET to the remote database server.

Requirement 3: The OOP and OOA pieces that build a list box within the accessible Form above to access the table names.

Requirement 4: The OOP and OOA pieces that parse the elements accessed within Requirement 3 to command line mode.

Requirement 5: The OOP and OOA pieces that update the column names by commit VB Script.

Now management can ask the development

Team of 1 or more (What happened to Requirement 4 and How long will the Change Request by use take to change, and

Estimate of cost and time! Each development build version can be tracked and monitored this way prior to release to user community.

http://192.168.1.1/1080/WebForm1.aspx.resx

The table above explains a generic relationship

Between OOP (Object Oriented Programming) and OOA (Object Oriented Analysis) we discussed briefly today in our meeting.

Each row above represents a generic representation of a Class:Object defined within the Program class {#} and the OOA column #, or element within the SQL matrix representation of the database which is made up of a [data connection + data adapter in VB.NET .NET

Where each Object Oriented Program will consist of a class name and database connection and adapter to query, update, and insert new table records.

Where Object Oriented Analysis of the interface of the database (in this case Structured Query Language is many rows and columns defined in multiple tables, generically defined by OOA(r#, c#)

Public Class OOP1

End Class

Public Class OOP2

End Class, etc. All Programs/classes will be defined at a High level for the Programmer and Analyst