//AMIS Technology Blog » Software Engineering » Page 4

Software Engineering

SIG Event

An evening about Maven

1
2 years ago
by Aino Andriessen in , , , ,

Recently we had a great session at AMIS about Maven, presented by Jason van Zyl, founder of the Apache Maven project and CTO of Sonatype. He gave us an overview of the new Maven 3 and other projects they are working on. In addition he gave us an insight in the world of Maven. For example, last three years, the usage of the Maven central repository has been doubled every year, with about 4 million unique IP addresses in 2009. They’ve also reorganized and improved the process for uploading artifacts to Maven central to a self service approach, using the staging function of Nexus Professional.

(more…)

Vacatures bij AMIS services

An Evening with Oracle Database Security Expert: Pete Finnigan

1
3 years ago
by Marco Gralike in , , , , ,

AMIS Technology School is proud to present, in collaboration with Miracle Benelux Masterclasses:

  • An Evening with Oracle Database Security Expert: Pete Finnigan on Tuesday 25th of May, 2010.

Miracle Benelux and Pete Finnigan agreed to do an extra special on the AMIS premises the evening just before Pete’s 2 day Masterclass in Utrecht will start (for the 2 day Masterclass agenda, see also the following URL). During this AMIS Query, besides the free food and normal standard setup of such an AMIS Query Event, Pete will have a presentation on Oracle security and there will be a lot of room of informal discussions during and after this session. There is still some room if you would like to learn from one of the best on Oracle database security.

More details on those masterclasses can be found on the Miracle Benelux site. Hopefully this will be the first of series… More details about this event will follow shortly.

About Pete Finnigan…

Pete is a world renowned expert in the area of Oracle security providing consultancy, design, security audits and trainings all in the area of Oracle Security. Pete is a member of the Oak table network, he has spoken regularly all over the world at More >

SIG Event

Automatic testing Oracle Service Bus using Hudson, maven and SoapUI

0
3 years ago
by Robbrecht van Amerongen in , , , , , , , , , , , , ,
A lot of current projects are implementing some sort of service based architecture. Testing in this architecture becomes more complex. When implementing an OSB project with Scrum you test-automation is imperative. Scrum will require more frequent testing of your system. This is only feasible (in time and money) when you automate as much as possible.   Using soapUI you are able to create visually SOAP tests on your OSB implementation and running them against the defined infrastructure (develop, test, acceptance).  SoapUI enables with easy tools to implements verification and validation of the responses of your OSB implementation. When running the test you are also able to set limits in SLA response times on all the calls. This way you are able to monitor depreciation of performance in older parts of your OSB implementation when adding new services.   You can record and edit your SOAP test easy with the soapUI interface and edit it later. When you maven-enable your project it is quite easy running your tests when you implement the “maven-soapui-plugin” (see my other posting http://technology.amis.nl/blog/3061/automated-soap-testing-with-maven).  In the meantime version 3.0 of More >
SIG Event

Agile software development, the principles. Principle 11: The best architectures, requirements, and designs emerge from self-organizing teams.

1
3 years ago
by Robbrecht van Amerongen in , , , , , , , ,
This is the eleventh of 12 posts about the principles of agile software development. Purpose is to go back to the start of the agile manifesto (http://agilemanifesto.org/principles.html) and discuss the implementation of the 12 principles in real life software engineering. Goals of agility are to go deliver software of higher quality, faster, with a higher acceptance to end-users and able to follow the changing business requirements to strive for competitive advantage.   The question is: is this going to work in practice or is this only based on a nice marketing and sales story.   Principle 11: The best architectures, requirements, and designs emerge from self-organizing teams.   For a long time the engineering expertise (and also software engineering) was based upon the condition that you worked with specialists. These specialists emerged from the principle of division of labour and made it possible for these specialists to focus their attention on their specialism and create the best solution within their field of expertise. The Interaction designer designed a user interface, the architect created a global systems model, developers created code and More >
SIG Event

Agile software development, the principles. Principle 10: Simplicity -“the art of maximizing the amount of work not done“- is essential

3 years ago
by Robbrecht van Amerongen in , , , ,

This is the tenth of 12 posts about the principles of agile software development. Purpose is to go back to the start of the agile manifesto (http://agilemanifesto.org/principles.html) and discuss the implementation of the 12 principles in real life software engineering. Goals of agility are to go deliver software of higher quality, faster, with a higher acceptance to end-users and able to follow the changing business requirements to strive for competitive advantage.

The question is: is this going to work in practice or is this only based on a nice marketing and sales story. Principle 10: Simplicity–the art of maximizing the amount of work not done–is essential. The KISS rule (Keep it stupid and simple) applies here. Simple things are easy to understand, and straightforward to implement. Simple things do not cost a lot of time (or money) to implement and are therefore also easy (painless) to revert. The middle part of this principle “maximizing the amount of work not done” is harder. When implementing agility in an organization this is the cause of discussion. Maximizing the work not done implies that the agile method will skip some processes, code and steps that where More >
SIG Event

Report from presentation ‘JPA 2.0 – What’s new’

3 years ago
by Emiel Paasschens in , , , , , , , ,

The Java Specification Request 317 (JSR-317) aka JavaTM Persistence 2.0,  (JPA 2.0) has finally reached the last stage, “Completion of Reference Implementation (RI) and Technology Compatibility Kit (TCK)”, before it’s officially released. Therefore last week a Knowledge Class was given at Amis with a presentation of the new functionality and differences compared to JPA 1.0 and some hands-on exercises. (more…)

Go to Top