technical

statement of work (SOW)

As Solution engineer I reviewed lots of A statement of works (SOW) used to have work done by a (prospective) supplier. The SOW was part of a Request for Proposals. I reviewed the SOW specific requirements from Software vendors or services companies at a very low level. Detailed requirements and pricing were usually specified in those.

semantic web - beyond web 2.0

As Solution engineer I reviewed lots of A statement of works (SOW) used to have work done by a (prospective) supplier. The SOW was part of a Request for Proposals. I reviewed the SOW specific requirements from Software vendors or services companies at a very low level. Detailed requirements and pricing were usually specified in those.

Software development kits (SDKs)

As Solution engineer typically I received the SDK from the source system developer to co-ordinate with the development team to create applications and services for the platform.

web services (XML)

As Solution engineer I typically supported the development team to design and develop interoperable machine-to-machine interactions - frequently just Web APIs that were to be accessed over the internal network or the Internet and executed on a remote system hosting the requested services embedded in a SOA architecture.

IT infrastructual

Of course I do have skills on soft- and hardware. Basics as MS Office incl. Visio, image editing, code editor, BPM on BPMN standard et al. may be named. Probably your are more interested in my secrect passion to serve as familiy's and friends' #1 Apple/MAC support...

mashups - screen scraping

Already in the 90's in my role as Product Manager at air travel consolidators, I have encountered the strength of data consolidation tools, but with the web 2.0 era the tools have gone a new dimension: Content used in mashups is typically obtained from a third party source through a public interface or API (web services). Other methods of obtaining content for mashups including feeds (e.g. RSS or Atom), and screen scraping were part of my Solution Engineering.

QA & CAT

Through out my projects I was supporting on test plans and testing of modules and components and supporting on customer deliveries, customer acceptance (CAT) and dealing with customer issues.

Schema and adapters

Typically as Solution engineer I co-ordinated the XSD from the source system and validated together with the development team against the platform's own XML schema.

Use Cases

In software engineering and systems design I normally used the use case technique to capture a system's behavioral requirements by detailing scenario-driven threads through the functional requirements.

UML

As Solution engineer I was creating and being supportive of designing a complex model (UML) to develop a global travel transactional platform (.NET)

o UML extended
- analysis (business cases – business processes)
- requirements/maintenance
- user interface (GUI)
o UML behavioural
- use cases
- activity
- communication
- sequence diagrams (flow charts)

functional specifications

As Solution engineer I was creating and reviewing functional specifications on a day to day basis, using proposal and requirement documentation as input.


 

home » skills » technical
Cookies allow me to offer my site. By using my site, you accept the use of cookies.  Accept